Apache Kafka Vs ActiveMQ

ActiveMQ and Kafka are two different kind of Messaging System. ActiveMQ has been for long in the industry with full stability and so rich feature whereas Kafka is the new beast which bring a totally new flavour to handle the large volume of data and high throughput.

Lets starts with the similarities and differencies between ActiveMQ and Apache Kafka

1) JMS : ActiveMQ is an implementation of JMS(Java Messaging Service) API whereas Apache Kafka is totally different distributed message system which uses its own protocol.

2) Performance : Message publishing speed in ActiveMQ is 300 msg/sec over  a single thread whereas Message publishing speed in Kafka is 165k  msg/sec over a single thread.

3) Message Ordering  :  Kafka ensures that the messages are received in the order in which they were sent at the partition level. JMS does not have any such contracts.

4) Persistence of Message : Kafka brokers store the messages for a specified period of time irrespective of whether the message has been picked up by the consumers or not.
JMS providers typically provide either in memory or disk based storage of messages.

5) Message Retrival : In ActiveMQ once the message is consumed and acknowledgement is being provided by the consumer , message is deleted from the queue whereas in Kafka old message can be retrived by  using the offset value.


These are all the few differences between the ActiveMQ and Apache Kafka . Although there is no comparison between them since both the queue belongs to totally different league.


When one should use ActiveMQ or when one should  use Apache Kafka :

Apache Kafka should be used in the scenario where throughput is very high and when one has to process very large volume of data per second .

ActiveMQ provides very rich features and used widely in most of the enterprise application with decent performance. If high thoughput is not your requirement then one can go with ActiveMQ.


This covers the concept of ActiveMQ and Apache Kafka comparison. If you have any question or you want to add anything please comment below.




Comments

Post a Comment

Popular posts from this blog

Deploy standalone Spring MVC Application in Docker Container

Image
In this post we will deploy simple standalone spring mvc application in Docker container. If you want to deploy the spring boot application in docker container, you can check my post Containerize Spring Boot application using Docker   . We know that in spring boot application there is embed Tomcat application server and run our app on top of it but in case of standalone spring mvc application we don't have embed Tomcat server , hence we need to deploy the application in explicit tomcat standalone server. Process to deploy the spring mvc in docker container : 1) First we need to get the Tomcat image. 2) Second to deploy the war in tomcat we need to save it in tomcat webapps direcory. Create Docker file  FROM : Using docker FROM command we are fetching the tomcat image from the Docker Hub. COPY : In the second line we are copying the war file in tomcat webapp directory. Note :  Any war saved in the tomcat webapps folder will be installed on tomcat start up. Yo
Read more

Refactor Code : Separate Query from Modifier

In this post we will learn about the one of the important code refactoring algorithm "Separate Query from Modifier" .When you have a method that gives you a value and has no observable side effects, you have a lot less to worry. You can move the call to other places in this method freely. A good rule to follow is to say that any method that returns a value should not have other observable side effects.  You have a method that returns a value but also changes the state of an object . Create two method, one for the query and one for the modification. We first take the example of the below and will find out what is wrong with this code and refactor it. In the above , method findMiscreant(List<Person> people) signifies that its responsibility will be to find miscreant only. But if we give clear look to the method , apart from finding Miscreant , it is sending some notification as   SendAlert()  to other system . Hence we can easily see that this method is doi
Read more

ConcurrentHashMap Internal Working

Image
ConcurrentHashMap utilizes the same principles of HashMap, but is designed primarily for a multi-threaded application and hence it does not require explicit synchronization.   The only thread safe collection objects were Hashtable and synchronized Map prior to JDK 5. Before learning How ConcurrentHashMap works in Java , we need to look at why concurrentHashMap is added to the Java SDK. Why we need ConcurrentHashMap when we already had Hashtable ? Hashtable provides concurrent access to the Map.Entries objects by locking the entire map to perform any sort of operation (update,delete,read,create). Suppose we have a web application , the overhead created by Hashtable  (locking the entire map) can be ignored under normal load. But under heavy load , the overhead of locking the entire map may prove fatal and may lead to delay response time and   overtaxing of the server. This  is where ConcurrentHashMap comes to rescue. According to ConcurrentHashMap Oracle docs, ConcurrentHashMa
Read more