If you are truly using IBM API Management for an API gateway, you will be ok. if you start trying to build custom scripts to transform messages complex in nature, it will soon become unmanageable.
Well suited for publishing internal services with very high security, protecting against attacks, and managing on-demand load. Also good for transform messages and SQL to Rest services. Not appropriate for business logic implementation.
Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy.
Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises.
API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth.
Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough.
Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling.
Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement.
The support team is good and the response time is reasonable, but (there is always a but), when support inquiries are made by someone experienced, and the question is not trivial, it is boring and takes a long time to get the case escalated to the next level of support.
There are a lot of similarities between Apigee Edge and IBM API Management. Some of the differences at the time of this posting is... 1) IBM APIM/C integrates better with other products. Dynatrace is used to track API and service specifics with the ability to offload those statistics for operational reporting. 2) If you are evolving from DataPower, IBM API Management is a logical choice to support additional REST APIs. 3) Generating keys is simple. Integration of those keys with a secure data vault is easy as well for your consumer.
We evaluated 3 tools and decided on Layer7 API Management because it had the shortest implementation times and fastest learning curve, without losing power of customization and scalability.
Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used.
Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients.
Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money.
