One of the most popular comparisons on IT Central Station is Apigee vs Mulesoft Anypoint API Manager
Which of these two solutions would you recommend and why?
Apigee hands down.
Previously tested both and MuleSoft took a couple weeks to understand how to build interfaces.
Two weeks to get our first REST to SOAP API up and running on MuleSoft.
Then we tried Apigee…
Found the menu was easy to navigate.
Pointed at our SOAP service, clicked a couple buttons and built.
Went to the test screen, entered the required parameters and BAM – worked.
Literally, five minutes and we were testing a working interface.
One company I worked for picked MuleSoft and none of the developers were happy.
Another company I worked for picked Apigee and the developers liked it.
P.S. Kubernetes over PCF all the way – execs need to ask real developers for their preference not just listen to marketing and sales guys.
I have worked on 5 API products each product has its own pros & cons. I would choose Apigee over all others because it provides pure API Management Tools & Services. Apigee also provides a lot of OOTB Policies which can be applied with little or no change. API Development & Exception handling is too easy in Apigee compared to Mulesoft.
Go for Mulesoft if ESB capabilities are required and unlike APigee we can do a lot of customization & create custom policies in Mulesoft. Mule also provides a lot of third-party connectors OOTB which can be used to quickly integrate with other systems. We can also create custom connecters as per our requirement.
Apigee supports Swagger & Mule supports RAML. So if your existing services/APIs produce/use Swagger go for Apigee. Anyway, we have many scripts which convert Swagger to RAML & vice-versa.
A very good Developer/API Portal is required for exposing the APIs securely & well-documented. If this is an important requirement, I would recommend Apigee over Mulesoft. Apigee's Drupal-based Portal provides a lot of features which Mulesoft Portal lacks.
Apigee also provides features/tools on Analytics & Bot-Detection for improving your APIs consumption.
Mostly worked with ApiGee Cloud and just evaluated MuleSoft.
MuleSoft great in providing lots of integration policies/beans out of the box (e.g. if you want to get direct access to S3 or Salesforce just take prepared policy and use). Flow design can be done both online (rather limited functionality) and offline (quite powerful but bulky Eclipse-based tool). Good enough analytics. Monetization should be plugged fro third-party provider.
ApiGee (Cloud) is easy to use, great support from the community, good enough online flow design tool. Great analytics (standard) and good monetization features (add-on).
For small/medium development teams who aren't specifically interested in integrations of numerous complicated data sources I'd rather suggest to go with ApiGee.
It depends on your needs. I would recommend Apigee if you are don’t need an Integration Platform/ ESB for any heavy lifting. Mulesoft Cloudhub comes with one common engine “Mule Anypoint Runtime Engine” which is the core and offers ESB capabilities including a lot of OOTB connectors.
Now if your southbound/ downstream has a lot of legacy applications requiring message/ file based integrations, then it makes sense to use Mulesoft, wrap these legacy-interfaces as HTTP/Web end-points and wire them using API Manager.
On the other hand, if you downstream is already on HTTP endpoint/ microservices, then Apigee is far more robust than API Manager. You can simply scale it to 200tps without any hassle. The deployment model of Apigee is lot cleaner as you can scale the “Message Processor & Message Router” (part of Edge gateway) separately from Dev Portal & Management server. The analytics is far superior to Mule and you far more options when wiring API than Mule. For example, the concept of IP-whitelisting, data policies (as filters) is pretty cool in Apigee. Another key point is you can have a hybrid model in Apigee with on-prem Message Router(s) to deploy multiple clusters of microservices. I have not used BaaS but it gives you the ability to create “Application Network” very similar to Mule except it looks richer.
Finally, with zookeeper, clustering of Apigee Edge server is more robust than Mulesoft, especially on higher loads. My verdict is Apigee if Integration is NOT a need.
BTW, I felt API Manager’s Anypoint Exchange is a better collaboration platform for sharing API definition within enterprise and outside. It's actually nice ?. But with Salesforce acquisition of Mulesoft, please understand their long-term roadmap and support/upgrade (especially if you going with On-Premise and not on cloud).
Unfortunately, I’m not in a position to recommend one way or the other. I’d personally go with CA’s API Management over either of these.
Interesting question. Both are gateways that I am confident in and both meet needs for Clients I work with.
I find both are not perfect API gateway offerings or rather others are more complete.
Rather than answer which gateway is better, or showcase all the differences, I think we have to start with what is your use case for the gateway.
Is the requirement for greenfield development or exposing an existing set of service?
Is the goal to gain control of the developers or enable citizen developers outside the organization?
Are you composing JSON API from multiple existing internal multiprotocol Services?
Are you proxying only for gathering metrics and analytics for your API usage?
Does the organization have a dedicated staff to only API support?
Depending on what you want to accomplish and the size of your organization and size of your API catalogs, different gateways suit you better.
As the number of micro-services grows into the thousands and hundreds of thousands different gateways standout.
The granularity of APIs provided by microservices is often different than what a client needs.
A gateway that facilitates composition of API from multiple downstream microservices can greatly accelerate adoption of the API.
The selection of the RIGHT API management software could best be described by choosing the one that matches the companies goals.
If a company really wants to control the API’s and their visibility to the citizen developers(read general public) then CA / IBM excel in this space.
If a company is wanting to have control but is more focused on making Microservice API’s useful and easier to use then TIBCO Mashery has a better Developer gateway.
Generally speaking, API product/offerings can be viewed as all similar but each having 3 main areas of Interest and specialization.
1. API Publisher portal (for use by admins) CA(layer7) and IBM leaders here
2. API Developer portal to learn system TIBCO Mashery is leader here
3. Proxy (API Gateway) does re-writing, format conversion, rate limiting (throttling). CA(layer7) is a leader here
The Leaders in each area come from their background
Mashery was a small company focusing on Agile development and API enabling developers
CA was Layer7 and they dominated the firewall/ external edge of companies parameters
IBM was (and is) all about control and has always been supporting companies operations
I know more about Mulesoft. I haven’t come across Apigee in many accounts, we mainly come across Mulesoft and IBM:
- Not a completely independent API Management Solution. Built to complement the Mule ESB component & it’s ESB is must for the API Solution to work.
- Too many different components & bulky deployment and heavy dependencies on its ESB.
- Very Limited Capability in terms of Traffic Aggregation, Security SDKs, Mobile/IoT Security & API Security Firewalling as compared to CA APIM.
- Very Limited capabilities in terms of Mobile Service Capability for app development & Mobile App Analytics.
- No Billing Integration for Monetization
- API product manager features, API design and creation, API transformation and integration are all limited compared to CA APIM.
- Requires considerable consultation & PS for implementation and to get the product work.
- No Mobile specific SDKs to build apps with end to end security, Mobile Single Sign On, Proximity Login (Session Sharing), Biometrics Login Capability, Pub/Sub Messaging, Geo-location based access, Adhoc User Groups Management in Mobile App etc. OOTB.
- Very Complex deployment with numerous components and needs a lot of supporting IBM components to function smoothly.
- Requires coding to achieve various API Policy use cases. Not a very easy drag/drop approach.
- Requires a lot of effort & considerable PS to implement the end-to-end API Lifecycle.
- Product primarily based on ESB and requires an IBM ESB component to function as desired.
- Primary a cloud solution, CA APIM has a full on-premise implementation
- The security features and tools that are impeded within CA APIM are extremely flexible and would be the best for an enterprise that requires a sophisticated architecture for the security processes and procedures
I hope this helps!
I am a Senior Information Technology Consultant for an Oil and Energy company.
We are currently evaluating Mulesoft Anypoint API Manager and WSO2 API Manager. What are the main differences between the two? Which do you recommend?
Thanks! I appreciate the help.
Which API Management tools have the best developer portal?
I'm looking for one with swagger and OpenAPI and modern content editor.