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.
Most of the time, server utilization is reliable and stable during peak times. Truly amazing, this product offers a lot and gets it done in no time without any confusion.It is reliable, too accurate and the performance is top-notch. It seems to be competitive in all virtual energy systems and its connectivity is also good. It's available at a low cost, but it's enough to have as many low-cost, more efficient systems as possible. It's a minor thing, but very rarely, it can cause work interruptions while it can get stuck due to more frequent use such as restless work. These power servers are very efficient and really help when things go wrong. I am using this product to retrieve data much faster.
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 IBM Z mainframe capabilities are unmatched for cloud readiness and optimization the learning capabilities are matched perfectly with Watson and the expandability of the cloud makes it a perfect choice.
Performance is a major part when you configure your system. IBM has many tools to study your system and suggest the appropriate configuration. With the right contract, you can add processing power dynamically and remove it when no longer needed
Support is usually superb, only occasionally dropping to very good. We participate in some of the CD (Continuous Delivery) aspects of z/OS, IMS, MQ, and DB2.
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.
IBM Z is the best storage solution as it provides the best in class data protection with the cryptographic hardware keys, no loss in data while migration, and a user-friendly interface that makes it easy for develops to understand and has less of a learning curve. This makes it well above the competition.
If you need more processing power, just add more CPU's or memory. The largest system can have close to 200 CPU's and 40 TB of memory. If that is not enough, you can add more physical computers, and connect them using a sysplex
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.
