最近在研究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, 不声明queue channel.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
# 声明exchange
channel.exchange_declare(exchange="logs", exchange_type="fanout")
# 不指定queue名字, rabbitmq会随机分配一个名字, 消息处理完成后queue会自动删除
result = channel.queue_declare(exclusive=True)
# 获取queue名字
queue_name = result.method.queue
# 绑定exchange和queue
channel.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, connection channel.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, connection
channel.exchange_declare(exchange="direct_test", exchange_type="direct")
result = channel.queue_declare(exclusive=True)
queue_name = result.method.queue
channel.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, connection
channel.exchange_declare(exchange="direct_test", exchange_type="direct")
result = channel.queue_declare(exclusive=True)
queue_name = result.method.queue
channel.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, connection
channel.exchange_declare(exchange="direct_test", exchange_type="direct")
result = channel.queue_declare(exclusive=True)
queue_name = result.method.queue
key_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.py python consumer01.py python consumer02.py python 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 sys from base import channel, connection # 声明exchange channel.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, connection
channel.exchange_declare(exchange="topic_test", exchange_type="topic")
result = channel.queue_declare(exclusive=True)
queue_name = result.method.queue
channel.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, connection
channel.exchange_declare(exchange="topic_test", exchange_type="topic")
result = channel.queue_declare(exclusive=True)
queue_name = result.method.queue
channel.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.py python 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.py python consumer02.py
结果:
consumer01.py没收到结果
consumer02.py的结果: body:b'this is a topic test'
通过这个例子我们就能明白topic的运行方式了。
参考自： https://www.jb51.net/article/150386.htm
以上就是本文的全部内容，希望对大家的学习有所帮助，也希望大家多多支持。
免责声明：本站文章均来自网站采集或用户投稿，网站不提供任何软件下载或自行开发的软件！ 如有用户或公司发现本站内容信息存在侵权行为，请邮件告知！ 858582#qq.com
《魔兽世界》大逃杀！60人新游玩模式《强袭风暴》3月21日上线
暴雪近日发布了《魔兽世界》10.2.6 更新内容，新游玩模式《强袭风暴》即将于3月21 日在亚服上线，届时玩家将前往阿拉希高地展开一场 60 人大逃杀对战。
艾泽拉斯的冒险者已经征服了艾泽拉斯的大地及遥远的彼岸。他们在对抗世界上最致命的敌人时展现出过人的手腕，并且成功阻止终结宇宙等级的威胁。当他们在为即将于《魔兽世界》资料片《地心之战》中来袭的萨拉塔斯势力做战斗准备时，他们还需要在熟悉的阿拉希高地面对一个全新的敌人──那就是彼此。在《巨龙崛起》10.2.6 更新的《强袭风暴》中，玩家将会进入一个全新的海盗主题大逃杀式限时活动，其中包含极高的风险和史诗级的奖励。
《强袭风暴》不是普通的战场，作为一个独立于主游戏之外的活动，玩家可以用大逃杀的风格来体验《魔兽世界》，不分职业、不分装备（除了你在赛局中捡到的），光是技巧和战略的强弱之分就能决定出谁才是能坚持到最后的赢家。本次活动将会开放单人和双人模式，玩家在加入海盗主题的预赛大厅区域前，可以从强袭风暴角色画面新增好友。游玩游戏将可以累计名望轨迹，《巨龙崛起》和《魔兽世界：巫妖王之怒 经典版》的玩家都可以获得奖励。