API Management Forum

Ariel Lindenfeld
Sr. Director of Community
IT Central Station
Jun 01 2018
One of our community members wrote that what's important is "proven reliability, responsiveness, scalability, security, ease of use...the tool should support a full lifecycle, from development to testing, deployment, monitoring and maintaining APIs, with real-time alerts and dashboards." What do you think? See other excellent answers here.  Let the community know what you think. Share your opinions now!
HernanHenriquezBelow you can find a list of elements I recommend to consider when evaluating this type of solutions. Security Gateway - Directory Authentication - API Security API Life Cycle Management -API Deployment Management Service Registry & Discovery - API Discovery - API Aggregation - Protocols/Message Support - Third Party Application Integration Performance Management - Traffic Management - Mobile Optimization - HTTP Acceleration and Data Caching - Load Balancing and HA and Resilience Analytics & Monitoring - API Monitoring - Email notifications (exchange) - Analytics Services Additional Capabilities/Characteristics - Availability - Support Model Key elements Security features to make sure the APis are secured against malicious attacks. another consideration is related to features to central manage a disparate set of APis, not matter they are exposed using the API management or not.
Siddharth SaxenaTo me the most important aspect is following. 1) Security of the gateway & APIs - Almost all API solution vendors offer nearly same security policy on the gateway. 2) Ease of use - Since this is niche and finding right talent is difficult and costly. This feature makes a difference. While evaluating we should ask question that how easy is to use this tool and train people. 3) Performance management and monitoring - It is very important to get timely info from the gateway on the events which are occurring and issues which may occur. 4) Life Cycle Management - This need to align with organizational policy with respect to usage of APIs
TobiFernandez
User
Which API Management tools have the best developer portal?I'm looking for one with swagger and OpenAPI and modern content editor.
Rhea Rapps
Content Specialist
IT Central Station
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? Thanks! --Rhea
Siddharth BI 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.
it_user423948Apigee 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.
Arnab SenguptaIt 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). Best Regards, Arnab.

Sign Up with Email