IBM API management enables creation and management of web application programming interfaces (API).
N/A
Anypoint Platform
Score 8.0 out of 10
N/A
The Anypoint Platform developed by MuleSoft and acquired by Salesforce in early 2018 is designed to
connect apps, data, and devices anywhere, on-premises or in the cloud. This platform was built to
offer out-of-the-box connectors as well as tools that architects and developers can adopt quickly to
design, build and manage the entire lifecycle of their APIs, applications, and products.
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.
MuleSoft Anypoint Platform is best tool in the market for developing APIs with complex structures communicating with various different types of applications including web applications as well as legacy applications. Also applications including database connectivity for fetching and updating data in the DB tables. I cant think of any scenario which MuleSoft Anypoint Platform could not be used for developing the integrations.
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.
Has more features than what we really need so we're paying for more than we use. Sort of like paying for an Abrams tank when all we really need is a Toyota Corolla.
Not a value product, tends to be expensive.
Takes a while for developers to learn to use Mulesoft Anypoint.
Anypoint Platform support is very responsive. There is also a huge knowledge base and an active online forum where answers to most questions can be found. When needed support engages the engineering group so adequate solutions or workarounds are always provided.
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.
Once we have moved all of our system integration APIs to the MuleSoft Anypoint Platform, we will need to communicate with a wide variety of external systems. All of our business and service logic is stored in the aforementioned core systems. Anypoint Platform (and all of our APIs) makes it easy to connect to various other platforms. In order to link to these many other systems, connectors and/or components are utilized, and they are simple to configure and integrate.
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.
