我想创建一个发布-订阅基础设施，其中每个订阅者都将收听多个（例如 100k）频道。
我认为使用 Redis PubSub 来实现此目的，但我不确定订阅数千个频道是否是最佳实践。
为了回答这个问题，我想知道 Redis 中的订阅机制如何在后台工作。
另一种选择是为每个订阅者创建一个通道，并在其间放置一些组件，该组件将获取所有消息并将其发布到相关通道。
还有其他想法吗？
Salvatore/Redis 的创建者在这里回答了这个问题：https://groups.google.com/forum/#!topic/redis-db/R09u__3Jzfk
All the complexity on the end is on the PUBLISH command, that performs
an amount of work that is proportional to:
a) The number of clients receiving the message.
b) The number of clients subscribed to a pattern, even if they'll not
match the message.
This means that if you have N clients subscribed to 100000 different
channels, everything will be super fast.
If you have instead 10000 clients subscribed to the same channel,
PUBLISH commands against this channel will be slow, and take maybe a
few milliseconds (not sure about the actual time taken). Since we have
to send the same message to everybody.
本文内容由网友自发贡献，版权归原作者所有，本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容，请联系:hwhale#tublm.com(使用前将#替换为@)
