Reviews (1-1 of 1)
IBM API Management is used for API lifecycle management - for creating, managing and securing APIs. It is an extension of the DataPower gateway used to manage cross-functional APIs and services. Used as an enterprise tool for socializing APIs through its discoverability and cataloging features. Performance, scaling and operational statistics are used to help identify hiccups or trends in service disruption.
- 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.
- 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.
Read Brent Heezen's full review
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.