Mule ESB vs. WSO2 API Manager

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Mule ESB
Score 8.4 out of 10
N/A
Mule ESB, from Mulesoft, is an open source middleware solution.N/A
WSO2 API Manager
Score 8.8 out of 10
Enterprise companies (1,001+ employees)
WSO2 API Manager is an open source solution for designing and publishing APIs. The solution also includes features for routing API traffic and creating and managing a community of developers. Since 2012, WSO2 has been working with customers from various industries, from Fortune 500 enterprises to ISVs, helping them solve their integration and innovation challenges through the use of APIs. The vendor says their customers also leverage the API Management…N/A
Pricing
Mule ESBWSO2 API Manager
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Mule ESBWSO2 API Manager
Free Trial
NoNo
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoYes
More Pricing Information
Features
Mule ESBWSO2 API Manager
API Management
Comparison of API Management features of Product A and Product B
Mule ESB
-
Ratings
WSO2 API Manager
8.5
4 Ratings
API access control00 Ratings9.44 Ratings
Rate limits and usage policies00 Ratings9.44 Ratings
API usage data00 Ratings7.44 Ratings
API user onboarding00 Ratings7.74 Ratings
API versioning00 Ratings9.04 Ratings
Usage billing and payments00 Ratings8.74 Ratings
API monitoring and logging00 Ratings7.94 Ratings
User Ratings
Mule ESBWSO2 API Manager
Likelihood to Recommend
9.8
(5 ratings)
9.1
(4 ratings)
User Testimonials
Mule ESBWSO2 API Manager
Likelihood to Recommend
Salesforce
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.
Read full review
WSO2
It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?
Read full review
Pros
Salesforce
  • 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.
Read full review
WSO2
  • Authentication based on OAuth 2.0 and HTTP Basic Authentication.
  • Rate Limiting applied at different levels like Subscriber, API, Resource and Backend.
  • Monitoring by exporting the metrics in Prometheus and traces in Jaeger.
  • Mediation to perform transformation, orchestration etc.
Read full review
Cons
Salesforce
  • 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
Read full review
WSO2
  • Better QA testing prior to releases rollout
  • Better support needed
Read full review
Alternatives Considered
Salesforce
It doesn't have API . We have to go for another API manager. But in Mule, it has both API manager and ESB
Read full review
WSO2
Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.
Read full review
Return on Investment
Salesforce
  • Overall a great tool for complex integrations
Read full review
WSO2
  • We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
  • Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
  • Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.
Read full review