What users are saying about
45 Ratings
27 Ratings
45 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.6 out of 101
27 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.4 out of 101

Likelihood to Recommend

Apache Kafka

Despite the disadvantages I list, I really believe that Kafka is the right choice whenever you need a queueing or message broker system. Kafka is way too battle-tested and scales too well to ever not consider it. The only exception is if your use case requires many, many small topics. Also, Kafka doesn't support delay queues out of the box and so you will need to "hack" it through special code on the consumer side.
No photo available

Mule ESB

If you’re bringing anything into Salesforce you should just invest now into Mule, you will get your money’s worth and find a myriad of uses to build APIs between many other systems. Once you build a component you can easily reuse it as a building block to attach to another source/destination. This makes it easy to ramp up quickly and spread usage of Mule throughout your enterprise. A good value for medium to large companies, but probably cheaper to outsource your job to a consulting firm if you are smaller.
No photo available

Pros

Apache Kafka

  • Apache Kafka is able to handle a large number of I/Os (writes) using 3-4 cheap servers.
  • It scales very well over large workloads and can handle extreme-scale deployments (eg. Linkedin with 300 billion user events each day).
  • The same Kafka setup can be used as a messaging bus, storage system or a log aggregator making it easy to maintain as one system feeding multiple applications.
No photo available

Mule ESB

  • It is best suited for Rest API development. Mule ESB uses RAML as an API descriptor which is less complex and easy to understand. RAML is an open standard majorly supported by Mulesoft. Once RAML is developed, it is very easy (a few clicks)to create flows corresponding to the resources defined in the RAML. One can also include JSON schema validation in RAML, and with the use of APIkit router, Mule ESB makes the request validation very easy (it's automatic basically.)
  • Mule ESB comes with a large spectrum of community and enterprise connectors. We have connectors for all the major platforms like Facebook, Twitter, Salesforce, SAP, etc. This enables Mule ESB to integrate with the other systems in a faster and more robust way. Mule ESB has many components to fulfill the requirements of each integration (for example batch processing, parallel processing, choice, etc.)
  • Mule API gateway is one of the best tools (modules) of Mulesoft's offering. It supports API governance and management very well. One can easily enforce policies on their APIs with API gateway. It enables some of the must-have features in an API solution (i.e. throttling, oAuth, access levels, etc.)
  • Implementing a CI/CD (DevOps) environment for Mule ESB is a very easy task. Mule majorly uses MAVEN as its build tool, which in turn makes it best suitable for CI/CD approach. Mule also provides MAVEN plugins for auto deployments to the servers. Mule also has a best Unit testing module which is MUnit. MUnit can be used for both Unit and Functional testing, and it is easy to write and generates coverage reports in various formats.
Deepak Kushwaha profile photo

Cons

Apache Kafka

  • Still a bit inmature, some clients have required recoding in the last few versions
  • New feaures coming very fast, several upgrades a year may be required
  • Not many commercial companies provide support
Juan Francisco Tavira profile photo

Mule ESB

  • Make sure to not over-engineer shared components. It can complicate development
  • Create a roadmap for where you are going - if not, you may miss components
  • I suggest getting support, otherwise it could be a difficult learning curve
No photo available

Likelihood to Renew

Apache Kafka

Apache Kafka 9.0
Based on 1 answer
Kafka is quickly becoming core product of the organization, indeed it is replacing older messaging systems. No better alternatives found yet
Juan Francisco Tavira profile photo

Mule ESB

No score
No answers yet
No answers on this topic

Support

Apache Kafka

Apache Kafka 10.0
Based on 2 answers
We use Heroku to host Pulsar and they have tons of Kafka experts that have helped us tune every little setting and give us advice via email or live chat (if you pay for premium support).
No photo available

Mule ESB

No score
No answers yet
No answers on this topic

Alternatives Considered

Apache Kafka

Confluent Cloud is still based on Apache Kafka but it has a subscription fee so, from a long term perspective, it is wiser to deploy your own Kafka instance that spans public and private cloud. Amazon Kinesis, Google Cloud Pub/Sub do not do well for a very number of messages and doesn't provide ordering guarantees as Apache Kafka or Confluent. Apache Kafka does better in scaling and availability than IBM MQ and Rabbit MQ.
No photo available

Mule ESB

It doesn't have API . We have to go for another API manager. But in Mule, it has both API manager and ESB
KamaL Vachiravel profile photo

Return on Investment

Apache Kafka

  • Kafka is free
  • Speeds up ingest
  • Faster for UI to get data
No photo available

Mule ESB

  • Overall a great tool for complex integrations
Ankit Goyal profile photo

Pricing Details

Apache Kafka

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Mule ESB

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Add comparison