Java Messages: Difference Between ActiveMQ, Mule, ServiceMix and Camel

Question

I am new to Messaging and want to know the difference between ActiveMQ , Mule , ServiceMix and Camel

Does anyone know how each of these products is different?

Thanks in advance!

EDIT: I would also like to know any good place / resource to learn these things.

Answer 1

ActiveMQ is a message broker that implements the JMS API and supports several multilingual clients and network protocols . This allows you to implement queues or topics and write listeners or subscribers to respond to queue events.

Mule and ServiceMix are an open source ESB (Enterprise Service Bus). An ESB has capabilities beyond JMS: queuing is a key factor, but transformations, routing, logging, security, etc. are also important.

Apache Camel is an implementation of templates in corporate integration templates. He can use JMS and other components to implement ideas from this book.

JMS is the foundation for other technologies, for example, JDBC is the foundation for Hibernate, iBatis, etc.

JMS is the Java API, as well as the specification and TCK (part of Java EE). ActiveMQ is a private implementation of this.

Camel can use ActiveMQ (and Camel is part of the ActiveMQ broker, so you can easily route JMS and other components supported by Camel).

Camel does not use Mule or ServiceMix directly; although ServiceMix uses Camel as its preferred routing and implementation mechanism for EIP. A camel has a ton of different components that use various technologies.

Answer 2

Let me first define

JMS is a J Ava M essaging S protocol specification.
ESB E Nterprise Ser B with us.
Reinforced concrete is J AVA B usiness i ntegration.

Now we can answer in more detail:

Apache ActiveMQ is an implementation of the above JMS (J Ava M essaging S y r).

Apache Camel is a message routing mechanism that implements enterprise integration patterns.
It provides many predefined components.
One of the key components supports JMS (J AVA M essaging Ser).

Apache ServiceMix is an implementation of the above ESB (E Nterprise Ser B with us)
compatible with JBI (J AVA B usiness i ntegration) specifications.
It also provides many infrastructure features not available in Camel (for example, OSGI package support).
SM makes extensive use of Camel.

Mule is another ESB implementation (E Nterprise Ser B with us), but not related to the Caramel / ServiceMix family.

Answer 3

Apache Service Mix :: Its ESB (Enterprise Service Bus), JBI container and integration platform.

Apache Camel: an intelligent routing and mediation mechanism that implements EIP (enterprise integration patterns).

Apache ActiveMQ: Its a message broker that implements JMS.

Answer 4

Mule is an Enterprise Service Bus providing a complete integration solution.

ActiveMQ is a message broker for priority messages between a subscriber and a recipient.

ServiceMix is ​​also an ESB, i.e. Enterprise Service Bus

Answer 5

Camel gives you the ability to define routing and mediation rules in different languages. Mule and SeriviceMix - ESB. ActiveMQ is a messaging service.

Answer 6

Apache Camel is an implementation of EIP (Enterprise Integration Templates)

ServiceMix is ​​an ESB-compliant SOA product.

Active MQ is no worse than any other JMS API implementation

Mule is also an ESB