Apache Kafka and IBM MQ are both messaging queue tools built to help IT systems communicate with each other in an asynchronous manner. Apache Kafka is designed to enable the streaming of real time data feeds and is an open source tool that users can access for free. IBM MQ is a traditional message queue system that allows multiple subscribers to pull messages from the end of the queue. Both tools are most popular with mid-sized businesses and large enterprises that are more likely to have complex IT infrastructures that need to communicate with each other.
Features
Both Apache Kafka and IBM MQ allow systems to send messages to each other asynchronously, but they also have a few standout features that set them apart from each other.
Apache Kafka utilized pull based communication, meaning that the receiving system requests a message from the producing system. This method of communication makes Apache Kafka faster than most traditional message queue systems. As businesses add more nodes to Apache Kafka, they will also find that it scales well, and notice few performance dips. Lastly, messages in Apache Kafka are not deleted upon the receiving system reading them, so it is easier to log events using Apache Kafka compared to other options.
IBM MQ is a more traditional message queue system that uses push based communication, in which a message producing system pushes its message into the queue and any receiver can consume it. This type of communication allows multiple systems to pull the same message from the queue at once. IBM MQ also includes several advanced features for security and message simplification.
Limitations
Though Apache Kafka and IBM MQ can both act as effective message borokers, they also have some limitations that are important to consider.
Apache Kafka can get a message from one system to it’s receiver quickly compared to traditional message queue tools, but each receiver must make a request for the message, rather than the producing system placing the message into an accessible queue. Additionally, while Apache Kafka can be used to log events and scales well, it doesn’t include as many granular features for security and message simplification. Apache Kafka is ideal for teams that value speed and performance highly.
IBM MQ is a robust traditional message queue system, but it doesn’t match the speed of Apache Kafka. Users should expect messages to take longer to complete in IBM MQ and will have a harder time using it to log events. As a result, IBM MQ is an ideal choice for businesses with complex IT infrastructures that often send messages from one system to many other systems, and who can benefit from granular customization features.
Pricing
Apache Kafka is an open source tool, so its pricing depends on the hosting service. Businesses should expect to pay at least $0.42 per hour, with that rate increasing as messaging needs increase.
IBM MQ is provided through IBM’s cloud service, pricing is dependent on the amount of client connections needed and users can reach out to the vendor for a detailed quote.
