ActiveMq message broker

Some userfull links I found on ActiveMQ

http://www.slideshare.net/dejanb/advanced-messaging-with-apache-activemq#btnNext
http://working-with-activemq.blogspot.com/2012/05/performance-improvements.html
http://www.javacodegeeks.com/2014/04/activemq-network-of-brokers-explained.html

RabbitMQ commands

To check the status of the RabbitMQ issue
sudo rabbitmqctl status

To stop the message broker issue,
sudo rabbitmqctl stop

To restart the message broker issue,
sudo invoke-rc.d rabbitmq-server start

Message broker or ESB?

Which one would you like to work with? or which one best suits with your requirement? Well in old traditional conceptions about both let me point out some key features.

A message broker is centralized (hub-spoke architecture) while an esb is not. Therefore a broker is a single point of failure. Again another fact is that a broker is only able vertical scaling and is unable to scale horizontally.

These are some articles I found on internet that describe this matter.

1. http://bradleyboveinis.com/2013/03/27/bus-vs-broker/
2. http://codebetter.com/drusellers/2009/05/29/why-messaging-5-bus-vs-broker/
3. http://msmvps.com/blogs/peterritchie/archive/2011/09/18/enterprise-service-buses-brokers-message-queues-oh-my.aspx

So the most popular and the winner seems to be the bus architecture.

Some popular opensource esbs are

1. Mule
2. Apache Synapse
3. Apache service mix
4. wso2 esb

There are some other software the enterpise integration patterns such as spring integration, apache camel. Now are they also called messaged brokers or esbs? Well you can think of them as just libraries that help to integrate enterprise software using enterprise integration patterns. Below is a link I found that addresses this matter.

http://camel.apache.org/is-camel-an-esb.html