Google Pub Sub/Lite vs RabbitMQ
我想面对我对Google Pubsub/Lite与RabbitMQ的理解(使用WSS上的MQTT)。
我的用例是我需要类似主题交换的东西。单独或全部或某些消息发送消息。
我知道我可以创建一个主题具有通过RoutingKey链接的多个队列。例如Amqtopic.RoutingKey1-10。 我可以将消息推向特定队列,例如这样的amqtopic.routingkey8 或将整个主题(所有队列都被路由)推入此时
。我不确定我是否想念什么。但是根据我的阅读,我倾向于拒绝,因为Google的工作就像直接交流一样。
谢谢您的帮助。
I would like to confront my understanding of google pubSub/lite vs RabbitMQ (using MQTT over WSS).
My use case is that I need something like a topic exchange. To send messages individually or to all or to some.
Having RabbitMQ I understand that I can create a topic have multiple queues linked via routingKey. E.g. amqTopic.routingKey1-10.
And I can push a message to a specific queue e.g. like this amqTopic.routingKey8
or push to the entire topic(all queues routed) like this amqTopic.*
Is it possible to create topic exchange structure with Google PubSub and if so how? I am not sure if I miss something. But from what I read I am inclined to say no, because google works like a direct exchange.
Thank you for helping..
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
这种主题交换结构可以使用Cloud Pub/sub filters 。您可以附加属性“ RutingKey”:“ 8” 或
“ RutingKey”:“ ALL”
)并在订阅上配置过滤器,以仅接收用于特定路由密钥的消息(attributes.Routibutes.RoutingKeykey =“ 8”或属性。RoutingKey=“ ALL”
在这种情况下)。目前不可能在Pub/Sub Lite中创建这种主题交换结构。
This kind of topic exchange structure is possible to re-create using Cloud Pub/Sub filters. You can attach attributes to your messages when they are published (e.g.
"routingKey": "8"
or"routingKey": "all"
) and configure filters on your subscriptions to receive only messages meant for a particular routing key (attributes.routingKey="8" OR attributes.routingKey="all"
in this scenario).It's not currently possible to create this kind of topic exchange structure in Pub/Sub Lite.