Skip to main content

WSO2 MB vs Apache Kafka comparison

When it comes to message broker solutions, those can be categorized into 2 main types
  • Standards based traditional message brokers (e.g. Apache ActiveMQ, RabbitMQ, WSO2 MB, Apache Qpid)
  • Proprietary modern message brokers (e.g. Apache Kafka, Kestrel)
Based on your requirement, you need to select the best category and then go for a specific vendor based on your needs, IT capacity and financial capabilities. In this post, I’m comparing 2 popular message brokers (WSO2 MB and Apache Kafka) from 2 categories. Even though it discusses about 2 specific brokers, you can consider this when comparing these 2 categories of message brokers.




FeatureWSO2 MBApache Kafka
Messaging semanticsRich messaging semantics with features such as
- Transactions
- Persistent/In-memory		Relaxed and proprietary
Supported protocolsJMS 1.0/1.1, AMQP, STOMP, MQTTPropreitary protocol written over TCP
Standard messagingsupports well known standards based messaging
- pub/sub
- request/reply
- point to point		Supports only pub/sub with proprietary protocol
ClusteringIn built clustering without any third party componentsRequires Zoo Keeper to make a cluster
PerformanceConsiderably low due to the standards based messaging semantics and different protocol supportHigher performance due to simpler messaging semantic and proprietary protocol
Deployment complexitySimpler deployment with 2 node cluster which is capable of handling a considerable loadComplex deployment with multiple components deployed in a cluster. Not suitable for moderate messaging requirements
Message flow controlSupported at the MB itself through
- dead letter channels
- QoS
- delivery guarantees		Needs to be done at the client side
Management consoleAvailable with full management capabilities of Queues/Topics and other server runtime monitoringNo native management console
Client supportJava, .Net, C++ and other AMQP clientsClients for Java, C++, Python, Go and others
Compatibilitycompatible with existing messaging systems within the enterprise due to standards based communicationNeed special connectors to be written for existing systems to connect with Kafka
SecuritySecurity can be configured through
- SSL at transport layer
- User based access control for queues
- Role based access control for topics		no SSL support







Based on the above comparison, if you are looking for a high performance, large scale message storage platform which works in isolation without much connectivity to existing systems, you can select Apache Kafka. But your requirements is to build a messaging system which interconnects with existing systems seamlessly and with a moderate performance and easily manageable deployment with rich messaging features, you can select WSO2 MB.
Cheers !!!
Labels:

Comments

Post a Comment

Popular posts from this blog

Understanding Threads created in WSO2 ESB

WSO2 ESB is an asynchronous high performing messaging engine which uses Java NIO technology for its internal implementations. You can find more information about the implementation details about the WSO2 ESB’s high performing http transport known as Pass-Through Transport (PTT) from the links given below. [1] http://soatutorials.blogspot.com/2015/05/understanding-wso2-esb-pass-through.html [2] http://wso2.com/library/articles/2013/12/demystifying-wso2-esb-pass-through-transport-part-i/ From this tutorial, I am going to discuss about various threads created when you start the ESB and start processing requests with that. This would help you to troubleshoot critical ESB server issues with the usage of a thread dump. You can monitor the threads created by using a monitoring tool like Jconsole or java mission control (java 1.7.40 upwards). Given below is a list of important threads and their stack traces from an active ESB server.  PassThroughHTTPSSender ( 1 Thread )
2 comments
Read more

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte
1 comment
Read more

WSO2 ESB tuning performance with threads

I have written several blog posts explaining the internal behavior of the ESB and the threads created inside ESB. With this post, I am talking about the effect of threads in the WSO2 ESB and how to tune up threads for optimal performance. You can refer [1] and [2] to understand the threads created within the ESB. [1] http://soatutorials.blogspot.com/2015/05/understanding-threads-created-in-wso2.html [2] http://wso2.com/library/articles/2012/03/importance-performance-wso2-esb-handles-nonobvious/ Within this blog post, I am discussing about the "worker threads" which are used for processing the data within the WSO2 ESB. There are 2 types of worker threads created when you start sending the requests to the server 1) Server Worker/Client Worker Threads 2) Mediator Worker (Synapse-Worker) Threads Server Worker/Client Worker Threads These set of threads will be used to process all the requests/responses coming to the ESB server. ServerWorker Threads will be used to pr
3 comments
Read more