是否有消息总线提供程序允许持久订阅者和完整重播？
我正在尝试找到一个支持 持久订阅者 并允许我重播的消息总线提供商根据消息时间戳对给定主题的所有消息进行排序。此外，我希望消息总线在消息延迟到达时重置每个持久消费者的检查点。例如，
- 客户端在 2009-12-22 12:00:00 订阅主题 1
- 消息 1 到达，时间戳 2009-12-22
- 客户端接收消息 1
- 客户端断开连接
- 消息 2 到达，时间戳 2009-12-21 18:00:00
- 客户端连接
- 客户端收到消息 2，然后收到消息 1
我强烈希望使用开源提供商。有谁知道支持此功能的消息总线提供商吗？我尝试阅读 ActiveMQ、Mass Transit 等的介绍文档，但我不得不承认我在消息总线术语方面落后于潮流，所以很多内容都超出了我的理解范围。
I am trying to find a message bus provider that supports Durable Subscribers and allows me to replay, in order, based on the message timestamp, all messages for a given topic. Futhermore, I would like the message bus to reset each durable consumer's checkpoint when a message arrives late. E.g.
- Client subscribes to topic 1 at 2009-12-22 12:00:00
- Message 1 arrives, Timestamped 2009-12-22
- Client receives Message 1
- Client disconnects
- Message 2 arrives, Timestamped 2009-12-21 18:00:00
- Client connects
- Client receives Message 2, then Message 1
I would strongly prefer an open source provider. Does anyone know of a message bus provider that supports this? I've tried to read the intro documentation for ActiveMQ, Mass Transit, etc but I have to admit that I am behind the curve on message bus terminology, so a lot of it went over my head.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
AMQP（由 RabbitMQ 等实现）允许您定义持久队列并将它们附加到同一个交换。每个想要接收消息的客户端首先建立自己的持久队列，即使客户端断开连接，该队列也会保存从交换器接收到的消息。
唯一的限制是从未连接过的客户端以及意外到达的客户端无法迟来地设置队列并请求转储所有先前的消息。 AMQP 1.0 可能允许这种通用持久性，但我不太了解新模型，所以我不能肯定地说。
AMQP (implemented by RabbitMQ, et al) lets you define durable queues and attach them to the same exchange. Each client that wants to receive messages first sets up its own durable queue, which will hold messages received from the exchange even while the client is disconnected.
The only limitation of this is that clients that have never connected, and which arrive on the scene unexpectedly, cannot belatedly setup a queue and request a dump of all previous messages. AMQP 1.0 might allow such universal persistence, but I don't know the new model that well, so I can't say for sure.
您可能想查看 spring 集成项目。
http://www.springsource.org/spring-integration
you may want to look at the spring integration project.
http://www.springsource.org/spring-integration