RabbitMQ与Mule相比如何 [英] How does RabbitMQ compare to Mule

问题描述

RabbitMQ与Mule相比如何，我将使用面向消息的体系结构构建应用程序，而AMQP(RabbitMQ)提供了我想要的一切，但是我却为众多相关技术选择和类似ESB之类的概念感到困惑.我怀疑我是否在不考虑其他选择的情况下做出选择.

How does RabbitMQ compare to Mule, I am going to build an application using message oriented architecture and AMQP (RabbitMQ) provides everything i want, but i am perplexed with so many related technology choice and similar concepts like ESB. I am having a doubt if i am making a choice without considering other alternatives.

我基本上清楚RabbitMQ是消息代理，它可以帮助我在生产者和消费者之间进行消息中介(所有形式或发布订阅，我可以从Twitter或Facebook更新等真实示例中了解其用法)

I am mostly clear that RabbitMQ is a message broker and it helps me in mediating message between producer and consumer (all forms or publish subscribe and i could understand how its used from real examples like twitter , or Facebook updates, etc)

什么是M子，如果我可以使用m子实现RabbitMQ的功能，我应该考虑与RabbitMQ类似的m子吗?

What is Mule, if i could achieve what i do in RabbitMQ using mule, should i consider mule similar to RabbitMQ?

m子的目的与消息代理的目的不同吗?

Does mule has a different objective than that of a message broker?

m子是否假设在其下面有一个消息代理，可以将消息传递到适当的m子侦听器(我可以轻松地在RabbitMQ中编写一个侦听器)

Does mule assumes that underlying it there is a message broker that delivers message to the appropriate mule listeners (i could easily write a listener in RabbitMQ)

是一个完整的Java基础系统(我用RabbitMQ进行的当前实验花了我不到30分钟的时间来编写一个简单的RPC客户端服务器，其客户端为C#，服务器为Java，这样的事情很容易在Mule中完成).

Is mule a complete Java bases system ( The current experiment i did with RabbitMQ took me less than 30 Min to write a simple RPC Client Server with client as C# and Server as Java , will such things be done in Mule easily).

推荐答案

Mule是ESB(企业服务总线). RabbitMQ是消息代理.

Mule is an ESB (Enterprise Service Bus). RabbitMQ is a message broker.

ESB 在消息代理之上提供了添加的层，例如路由，转换和业务流程管理.它是应用程序之间的中介者，它集成了Web服务，REST端点，数据库连接，电子邮件和ftp服务器-您可以为它命名.这是一个高级集成骨干，可在说不同协议的应用程序网络内协调互操作性.

An ESB provides added layers atop of a message broker such as routing, transformations and business process management. It is a mediator between applications, integrating Web Services, REST endpoints, database connections, email and ftp servers - you name it. It is a high-level integration backbone which orchestrates interoperability within a network of applications that speak different protocols.

消息代理是一个较低级的组件，它使您作为开发人员能够在发布者和订阅者之间(通常在同一系统的组件之间，但并非总是)中继原始消息.它用于启用异步处理，以缩短响应时间.有些任务需要更长的时间来处理，如果它们对时间不敏感，则您不希望它们拖延时间.而是将消息发布到队列(作为发布者)，然后让订阅者将其拾取并稍后"处理.

A message broker is a lower level component which enables you as a developer to relay raw messages between publishers and subscribers, typically between components of the same system but not always. It is used to enable asynchronous processing to keep response times low. Some tasks take longer to process and you don't want them to hold things up if they're not time-sensitive. Instead, post a message to a queue (as a publisher) and have a subscriber pick it up and process it "later".

这篇关于RabbitMQ与Mule相比如何的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！