通过服务总线查询
是否建议也通过服务总线进行查询？在我看来，你应该只发送火并忘记命令/事件。
您的意见和/或经验是什么？
Is it recommended to also do querying via a Service Bus? As I see it, you should only send fire and forget commands/events.
What is your opinion and/or experience?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
服务总线不仅适用于“即发即忘”场景。事实上，它可以用于许多其他用途，例如“请求响应”。但与传统的远程过程调用或调用相比，服务总线提供了将实际请求者与实际响应者分离的方法。这为更轻松的可扩展性和/或提高弹性打开了大门。
有大量关于消息传递和服务总线模式主题的帖子、文章和书籍，并且将提供有价值的见解和想法。只需寻找服务总线或消息队列集成、模式。
Service bus is not only suited to "fire and forget" scenarios. In fact it can be used in many others like "request response". But in contrast to classic remote procedure calls or invocations, service bus provides means to decouple actual requester from actual responder. And that opens the door for easier scalability and/or improved resilience.
There are plenty of posts, articles and books written on the subject of messaging and service bus patterns, and will provide valuable insights and ideas. Just look for service bus or message queue integration, patterns.
查询到底是什么意思？从数据库中检索数据？聚合来自多个服务的多重响应？所有这些事情都可以通过 Service Bus 很好地完成。一些特定产品（例如 WebSphere ESB 或 Oracle Service Bus）提供生成数据库适配器的能力，这些适配器可以从表中检索数据或调用存储过程。
What exactly do you mean by queruing? Retrieving data from database? Aggregating multiplie responses from several services? All those things are done quite good with Service Bus. Some specific products like WebSphere ESB or Oracle Service Bus offer ability to generate database adapters which can retrieve data from tables or call stored procedures.