python实现RabbitMQ的消息队列的示例代码
Python  /  管理员 发布于 6年前   213
最近在研究redis做消息队列时,顺便看了一下RabbitMQ做消息队列的实现。以下是总结的RabbitMQ中三种exchange模式的实现,分别是fanout, direct和topic。
base.py:
import pika# 获取认证对象,参数是用户名、密码。远程连接时需要认证credentials = pika.PlainCredentials("admin", "admin")# BlockingConnection(): 实例化连接对象# ConnectionParameters(): 实例化链接参数对象connection = pika.BlockingConnection(pika.ConnectionParameters( "192.168.0.102", 5672, "/", credentials))# 创建新的channel(通道)channel = connection.channel()
fanout模式:向绑定到指定exchange的queue中发送消息,消费者从queue中取出数据,类似于广播模式、发布订阅模式。
绑定方式: 在接收端channel.queue_bind(exchange="logs", queue=queue_name)
代码:
publisher.py:
from base import channel, connection# 声明exchange, 不声明queuechannel.exchange_declare(exchange="logs", exchange_type="fanout") # 广播message = "hello fanout"channel.basic_publish( exchange="logs", routing_key="", body=message)connection.close()
consumer.py:
from base import channel, connection # 声明exchangechannel.exchange_declare(exchange="logs", exchange_type="fanout")# 不指定queue名字, rabbitmq会随机分配一个名字, 消息处理完成后queue会自动删除result = channel.queue_declare(exclusive=True) # 获取queue名字queue_name = result.method.queue# 绑定exchange和queuechannel.queue_bind(exchange="logs", queue=queue_name)def callback(ch, method, properties, body): print("body:%s" % body)channel.basic_consume( callback, queue=queue_name)channel.start_consuming()
direct模式:发送端绑定一个routing_key1, queue中绑定若干个routing_key2, 若key1与key2相等,或者key1在key2中,则消息就会发送到这个queue中,再由相应的消费者去queue中取数据。
publisher.py:
from base import channel, connectionchannel.exchange_declare(exchange="direct_test", exchange_type="direct")message = "hello"channel.basic_publish( exchange="direct_test", routing_key="info", # 绑定key body=message)connection.close()
consumer01.py:
from base import channel, connectionchannel.exchange_declare(exchange="direct_test", exchange_type="direct")result = channel.queue_declare(exclusive=True)queue_name = result.method.queuechannel.queue_bind( exchange="direct_test", queue=queue_name, # 绑定的key,与publisher中的相同 routing_key="info" )def callback(ch, method, properties, body): print("body:%s" % body)channel.basic_consume( callback, queue=queue_name)channel.start_consuming()
consumer02.py:
from base import channel, connectionchannel.exchange_declare(exchange="direct_test", exchange_type="direct")result = channel.queue_declare(exclusive=True)queue_name = result.method.queuechannel.queue_bind( exchange="direct_test", queue=queue_name, # 绑定的key routing_key="error" )def callback(ch, method, properties, bosy): print("body:%s" % body)channel.basic_consume( callback, queue=queue_name)channel.start_consuming()
consumer03.py:
from base import channel, connectionchannel.exchange_declare(exchange="direct_test", exchange_type="direct")result = channel.queue_declare(exclusive=True)queue_name = result.method.queuekey_list = ["info", "warning"]for key in key_list: channel.queue_bind( exchange="direct_test", queue=queue_name, # 一个queue同时绑定多个key,有一个key满足条件时就可以收到数据 routing_key=key )def callback(ch, method, properties, body): print("body:%s" % body)channel.basic_consume( callback, queue=queue_name)channel.start_consuming()
执行:
python producer.pypython consumer01.pypython consumer02.pypython consumer03.py
结果:
consumer01.py: body:b'hello'
consumer02.py没收到结果
consumer03.py: body:b'hello'
topic模式不是太好理解,我的理解如下:
对于发送端绑定的routing_key1,queue绑定若干个routing_key2;若routing_key1满足任意一个routing_key2,则该消息就会通过exchange发送到这个queue中,然后由接收端从queue中取出其实就是direct模式的扩展。
绑定方式:
发送端绑定:
channel.basic_publish( exchange="topic_logs", routing_key=routing_key, body=message )
接收端绑定:
channel.queue_bind( exchange="topic_logs", queue=queue_name, routing_key=binding_key )
publisher.py:
import sysfrom base import channel, connection# 声明exchangechannel.exchange_declare(exchange="topic_test", exchange_type="topic")# 待发送消息message = " ".join(sys.argv[1:]) or "hello topic"# 发布消息channel.basic_publish( exchange="topic_test", routing_key="mysql.error", # 绑定的routing_key body=message)connection.close()
consumer01.py:
from base import channel, connectionchannel.exchange_declare(exchange="topic_test", exchange_type="topic")result = channel.queue_declare(exclusive=True)queue_name = result.method.queuechannel.queue_bind( exchange="topic_test", queue=queue_name, routing_key="*.error" # 绑定的routing_key)def callback(ch, method, properties, body): print("body:%s" % body)channel.basic_consume( callback, queue=queue_name, no_ack=True)channel.start_consuming()
consumer02.py:
from base import channel, connectionchannel.exchange_declare(exchange="topic_test", exchange_type="topic")result = channel.queue_declare(exclusive=True)queue_name = result.method.queuechannel.queue_bind( exchange="topic_test", queue=queue_name, routing_key="mysql.*" # 绑定的routing_key)def callback(ch, method, properties, body): print("body:%s" % body)channel.basic_consume( callback, queue=queue_name, no_ack=True)channel.start_consuming()
执行:
python publisher02.py "this is a topic test"python consumer01.pypython consumer02.py
结果:
consumer01.py的结果: body:b'this is a topic test'
consumer02.py的结果: body:b'this is a topic test'
说明通过绑定相应的routing_key,两个消费者都收到了消息
将publisher.py的routing_key改成"mysql.info"
再此执行:
python publisher02.py "this is a topic test"python consumer01.pypython consumer02.py
结果:
consumer01.py没收到结果
consumer02.py的结果: body:b'this is a topic test'
通过这个例子我们就能明白topic的运行方式了。
参考自: https:///article/150386.htm
以上就是本文的全部内容,希望对大家的学习有所帮助,也希望大家多多支持。
123 在
Clash for Windows作者删库跑路了,github已404中评论 按理说只要你在国内,所有的流量进出都在监控范围内,不管你怎么隐藏也没用,想搞你分..原梓番博客 在
在Laravel框架中使用模型Model分表最简单的方法中评论 好久好久都没看友情链接申请了,今天刚看,已经添加。..博主 在
佛跳墙vpn软件不会用?上不了网?佛跳墙vpn常见问题以及解决办法中评论 @1111老铁这个不行了,可以看看近期评论的其他文章..1111 在
佛跳墙vpn软件不会用?上不了网?佛跳墙vpn常见问题以及解决办法中评论 网站不能打开,博主百忙中能否发个APP下载链接,佛跳墙或极光..路人 在
php中使用hyperf框架调用讯飞星火大模型实现国内版chatgpt功能示例中评论 教程很详细,如果加个前端chatgpt对话页面就完美了..Copyright·© 2019 侯体宗版权所有· 粤ICP备20027696号