Apigee Edge vs. Mule ESB

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apigee Edge
Score 7.8 out of 10
N/A
Apigee Edge is an API management platform now owned and offered by Google, since Google acquired Apigee in 2016.N/A
Mule ESB
Score 9.0 out of 10
N/A
Mule ESB, from Mulesoft, is an open source middleware solution.N/A
Pricing
Apigee EdgeMule ESB
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apigee EdgeMule ESB
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apigee EdgeMule ESB
Considered Both Products
Apigee Edge
Chose Apigee Edge
Somewhere in the middle. Based on its current offerings and subscription model
Mule ESB

No answer on this topic

Top Pros
Top Cons
Features
Apigee EdgeMule ESB
API Management
Comparison of API Management features of Product A and Product B
Apigee Edge
9.4
7 Ratings
12% above category average
Mule ESB
-
Ratings
API access control9.07 Ratings00 Ratings
Rate limits and usage policies9.07 Ratings00 Ratings
API usage data9.07 Ratings00 Ratings
API user onboarding9.97 Ratings00 Ratings
API versioning9.97 Ratings00 Ratings
Usage billing and payments9.06 Ratings00 Ratings
API monitoring and logging9.97 Ratings00 Ratings
Best Alternatives
Apigee EdgeMule ESB
Small Businesses
NGINX
NGINX
Score 9.1 out of 10

No answers on this topic

Medium-sized Companies
NGINX
NGINX
Score 9.1 out of 10
Anypoint Platform
Anypoint Platform
Score 8.3 out of 10
Enterprises
NGINX
NGINX
Score 9.1 out of 10
Anypoint Platform
Anypoint Platform
Score 8.3 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apigee EdgeMule ESB
Likelihood to Recommend
9.0
(7 ratings)
9.8
(5 ratings)
Likelihood to Renew
9.0
(1 ratings)
-
(0 ratings)
Usability
9.0
(1 ratings)
-
(0 ratings)
Support Rating
6.0
(1 ratings)
-
(0 ratings)
User Testimonials
Apigee EdgeMule ESB
Likelihood to Recommend
Google
Few scenarios 1. For viewing API analytics, I think it is best in the market 2. For earning money via API monetization 3. Securing API 4. Onboarding legacy APIs to provide modern REST endpoints
Read full review
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
Pros
Google
  • Better exception handling with the Raise exception policies help to monitor the flow by setting up the flow conditions.
  • Easy development of a Proxy and APIs with much less tutoring and helps make getting started for new users easy.
  • Very good documentation and blog with details of most common failures and error handling.
  • A very very easy to use console.
Read full review
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
Cons
Google
  • Only one user can be active in a proxy at a time
  • No version control
  • Prohibited from using JSON.stringify on Apigee objects (tokens)
  • Debugging is difficult
  • Unable to rename or delete policies without bumping revision
  • Why would anyone give a js policy one name, display name something else, and script a different name?
  • 'Trace' limited to only 20 transactions
  • UI allows users to add target servers, but users must utilize the api to turn on SSL.
  • I'm sure there's more, they just aren't coming to mind right now.
  • Apigee forgets (expires?) your password at random intervals without notice. Every few weeks, or days, sometimes even three times in one day, I'll attempt to login to Apigee and my password will be 'wrong'. I've reset my password and Apigee still claims it's wrong. I've had to reset my password three times before it finally let me log back in.
Read full review
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
Likelihood to Renew
Google
I am not the one deciding whether to use apigee or not really. But personally, I would recommend the use of it as developing APIs on it is easy. And as a mediator between backend servers, we could easily modify request and responses in it without touching any backend code while having a centralize gateway to access our backend APIs too.
Read full review
Salesforce
No answers on this topic
Usability
Google
Support has helped us to resolved all the queries and community support was also good.
Read full review
Salesforce
No answers on this topic
Support Rating
Google
Quite hard to get support, at least on the coding side, when we encounter blockers. But general concerns, they would schedule a call to you for them to get a whole picture of your concern. Albeit in my experience, bad really as they haven't replied about the progress, but otherwise seems to have been fixed.
Read full review
Salesforce
No answers on this topic
Alternatives Considered
Google
Apigee is the best in the market in terms of API Analytics Apigee is having wonderful Documentation with short videos Security is a major concern and Apigee provides an easily configurable policy to secure API Quota and rate-limit is again very easy to configure on every API basis It provides various policies to transform the response from one form to another form e.g. JSON to XML or XML to JSON
Read full review
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
Return on Investment
Google
  • As a public entity it is hard to say how much ROI we can have. We have yet to create a billing and ROI plan. We are thinking of other ways to create ROI, possibly through data/service barter.
Read full review
Salesforce
  • Overall a great tool for complex integrations
Read full review
ScreenShots