IBM API Connect Reviews

APIC as an APIM product suite is a complete tool for API management and for microservices as well. I liked the control it gives to the governance and the analytics for product owners which is critical for product design and pricing. From a security and management point of view, I like the space management within the catalogs. The built-in policies security, mediation and transport are well defined.

There could have been more policies in the security section, a little better UI because sometimes it becomes little too confusing to browse through the different features. There should be a recovery process for lost API secret for app consumer. If they forget to copy paste their client secret then its tough on them.

The APIC is being used for enabling the interdepartmental communication by exposing the services as API which need a minimum transformation and primarily read-only in nature. Some of the services are also exposed to external partners to fetch data.

Of the 1700+ APIs we Service, of the 600+ teams developing those services, with all the traffic they can produce, the Management alone is fluid, functional, stable, easy to task, and monitor or track. Providing "Consumer" Applications and Backend Service Developers the space/time they need independently to develop and advace their services, develope their product, increase their feature stack, and provide changes at better rates than typicle 'client - server' relationships/infastructure/arcetecture.

Its a simplified service with simple demands and simple archetecture, that QUICKLY can become a 'beast' to move/migrate/manipulate when a known "feature" is redicovered, or new fundamental change is rolled out. Dramatic, Visible, and Orcastrational changes can impact consumers and developers with what appears to be a whole new Product rather than an updated more current and 'intune' verson.

Deploying APIC as a Midileware service, to allow for Fontend and Backend service Developers to Change on independent timelines. Consumers can see opportunities in other products that are more adequate to their use-case and drive development better, because the ease of change is available.

It is every easy to understand how to create an API and also publish it. The documentation of API Connect is nice as well.

It is very hard to debug a policy once it created. I would like to have the same possibility to debug as you get in the IBM Integration Bus, to be able to see the different headers and the message body.

The way of making applications more accessable.

For me the best feature is that gateway is run on Datapower and it is reliable and easy to develeop and administer the product. Basing main deployment artefacts on open specifiaction and extending with custom stuff is a way to go. This enable implementation CI/CD processes.

Sometimes analytics gathering is broken and we have incosistent analytics data. Restart of manager VM and/or DP domain helps. Not a blocker for me but it would be nice if it would be fixed.

Implemented strangler pattern by exposing large custom build Entreprise system as a set of well defined APIs so we can break the monolith into something more managable.

IT gives us analytics, makes exposing APIs to clients much easier, it gives us a central point for consuming and managing APIs

The fact the whenever we have to upgrade datapower, we have to delete the gateway server from API connect then re add it again after the datapower upgrade. I wish this dependency will be removed in the future as it is a bit disruptive and doing firmware upgrades should be as simple and transparent as possible

We purchased API Connect so we have a central point to manage APIs. It also made it easier for us to expose our APIs to consumers.

Ability to API enable our core assets, and sunset several other API tools such as API Manager, APIgee, WSRR.

When we started implementing API Connect, there was no elegant way to just do discovery the services. I believe my tech team has been working to get that issue resolved.

Democritizing data; breaking monoliths into micro services to enable agility.

Love that we are moving to a unified platform to house all of our organizations API's. Certainly beats trying to determine whether an API already exists. We have just begun to roll this out across the organization and it has been incredibly well received.

Like anything it takes time to roll out any new technology - while we are moving it would be great to move much quicker.

1. Providing us visibility and accessibility for our APIs managed in one place.

2. Benefits - everyone wants to use it and adoption has been incredibly high.

It fits perfect for all the Bank industry in order to offer data as a service

The cost, it a long way to get the ROI, for middle size bank it is an expensive bit

B2B businees is being a challenge for banks, it has to be a easy way to get our customers connected

security and ease of use, allows developers out of Integration to do integration

in v5 you donot have too much control, you have to keep calling IBM, and the response time is not too good.

No Load balancer groups On APIM

Go with the Latest Version

allowing feature teams ro do their own integration

It is a great api management solution with rich set of management and self service features. With Datapower as runtime it fits well in on prem for exposing in house APIs to internal and external developers. We are moving towards v2018 on kubernetes platform and we hope it will add more values.

Installation on API Connect on VMWare OVA as well as on kubernetes is not properly documented.

Faster development by exposing the APIs.

Service availability and discovery.

Centralized self service portal for multi cloud environments.

Organization brand reach.

Security capabilities, multe-tenancy capability of the portal, hybrid deployment capabilities of the runtime component

There are no features to dislike especially when it is completely re-architected in the 2018 version with underlying microservices architecture

Multi-tenancy no the portal, API life cycling, role based development, unified security Use Cases implementation

DataPower Gateway, ease of use, extensible

Limited monitization support, no direct migration path available from v5.0.5 to 2018.x

APIConnect is a good product with DataPower as a security gateway

Exposing legacy functions as api's for faster time to market. IBM APIConnect has helped us stay ahead in the race

they were able to understand the specific requirements of our organization and were able to customize the product to suit the security model including the authentication and authorization, sso and use out=r LDAP for all this

had bugs when the install was happening, but the same were resolved in a timely manner and lot of attention was provided by the product development team

we were able to expose several APIs to the larger audience, reduce redundancy, were able to restrict the api usage, monitor the analytics

The ability to handle things with ease. Great directional assistance with easy to understand steps. IBM is always looking for better ways of perfecting it's products.

I have no dislikes at all. My experience has been one of gaining knowledge and experience inside the Artificial intelligence world.

Great security for my business

the ensamble area is easy to create a api in less 15 minutes

sometimes when i publish a product in api gateway is sometimes slow.

after, we had a lot ways to connect with banking core, but now we have one way to get specific data.

We moved our API management from a custom approach to an industrial product like API Connect and that's when we thought about all the features we were missing with our previous product.

What I don't like very much is the statistics UI but we moved all of our logs to syslog.

With PSD2 european directive all the banks will have to expose their client's data to other third parties.

We are using IBM API Connect to fullfil this requirement.

User frienfly UI based API implementation.

Developer portal with giving developers/api consumers every single detail about the API.

Gatewayscript should have something like Intelli sense and proper code display notifications like any Java IDE.

Integrating business to other businesses by giving developers everything they need within single portal acces.

The ease and speed that you can develop new APIs is amazing. The interface is very user-friendly and makes sense from a software development standpoint.

Setting up the system locally took some learning.

Quick and easy creation of APIs for microservices.

We required the functionality of an API Manager and API Connect answered 95% of all our requirements

Extremely difficut to customize the UI that we had to work with an IBM partner to modify it to suit our requirements

Its functionality is ex ceptional, but check the price and the ease of customization.

We were able to monetize our financial functionality and use a single platform for all our internal applications requiring access to our core systems

Easy to configure, secure and expose APIs

Good set of security features out of the box

Does not fully support our change implementation strategy for product upgrades

No native HSM support other than Luna (which doesnt support HA)

We have had to write extensions for native features not currently available in v5

Open Banking APIs exposed to regulated TPPs

Interal APIs exposed to key channels (e.g. internet banking)

Ease of onboarding

Data insights and market intelligence

API Connect is easy to use and makes a non technical person able to use it.

The product is quiet good there isnt anything so far that I see as a problem

Try it you will love it

API management is always a pain in a software engineering firm like ours, and I want my developers to be able to hit the ground running and not spend too much time doing non core stuff.

I am fairly new to this space and this service is very user friendly.

I do not have any dislikes at this time.

We are the first to utlize the cloud in the Opthamology space.

The facility to deploy an API, the interoperatibility with diferents technologies

Its kinda tricky to upgrade even to install. This processes were a big headache to us

Exposes API's to external clients and costumers.

The easy inplementation, integration with other applications and back-end applications

None at this poingt since we just went live with it

The easy implementation enables us to bring new API's live easily

I liked the intergration of multiple systems and the ability to have info availble for data sharing.

The time that it takes to get the data avilable for sharing amongst teams

Helathcare.

it is based on datapower . same product can go on the cloud and on prem

no intelligent context sensitive search

no tam/tfim integration

Vehicle apis

MUlti Cloud deployments

Extensive support for plans, spaces,catalogs.

Flexible archtiecure of key components

Migration from one version to another is not seamless

2018 version installation is not straight forward

I would recommend API Connect due to its strong gateway & Developer Portal features.

Expose API's to Partners & Developers and Internal consumers.

Centrailized discovery of API's

partner management

developer friendly , easy to use , out of box analytics , cloud native,auto scalling and elasticity

missing auto healing, client side load balancing, still auto scalling and elasticity is maturing

easy to use and very good compared to other products in the market

exposing backend services as APIs, rate limiting , security, SSO

It has helped our organization start a transformation and will continue to for many years in the future

Like any enterprise system this is overly complicated to install and get started

Moving our middleware stack from a custom home grown to a platform that enables us to the use a lifecycle approach

It is intuitive. It has range spectrum of embedded product that is needed. I like API security configuration options. Developers portal is intuitive. Easy to install.

Security token is not easy to integrate in solution. Needs lot of configuration.

REST API exposure for external consumption.

New architecture with the Docker. Ability to deploy to the multiple clouds. Support for various of loads and security features.

Not enough information how to deploy it to the some third party clouds.

Plan cloud or local installation

Exposing APIs in public sector

Easy deployment of RESTful APIs, easy pont of security enhancement

enhanicing datapower infratsructure

unreadyness of the product

support cases (usally 3/5 in parallel) are not always solved

start with Version 2018, not V5

providing API universe to internal and external customers

The capacity to integrate easily with microservices developed on NOde.js

It was difficult to implement it.with a In-house team.

Great specially for those that do not have moved completly to the cloud.

Integration with our legacy systems

Works well in our envrionment. We hav ebeen using thisn product for the past 5 years and works well

There is nothing we don't like about this product.

We are suing this product for managing APIs performance

I love the power an security included in the product. Also it has an amazing monetization control. Its a helpfull tool for Digital Transformation.

by now, i don't have any dislike on this product. ...

Digital Transformation

The time to write a new API is faster than traditional coding

Product still seems still have many bugs as it grows and develops

We are exposing legacy services as up to date rest APIs

Seamless creation & Management. Ease of using a sophosticated technology

It is difficult to propose it to the customers as the price is a little on the higher side

Go for It

Agility

Robustness

Connectivity

Redily available OEMs for installation. Available developement starter kit.

Supportx only Java and NodeJS developement. Python should be there.

Exposing the internal data to other systems so that there is always one source of truth

Cloud and Kubernetes support is good , Extending to IBM Cloud and other clouds. Docker support

API Connect being stable, having issues with being able to be stable.

API , Secuirty , throtle

East to install, configure and onboard API and Applicaton developers.

Proprietary applicance hard to resolve issues.

Purchase Premier Support or On Demand Consulting,. Standard support for IBM API Connect lacking.

API Enablement

Integration with datapower and support from the ibm team.

We've had many problems using the product itself that have not been fixed.

We are trying to move to an api economy.

Supports devops integration

API Management

Out of the box analytics needs to be improved

Difficult to debug

Advanced integration features unavailable unless purchased with DataPower appliance

API Integration

API Management

it ease of use on API manager and easy config on datapower

developer portal needs work, the interface should have single signon and additional functionalities for templates

mostly with configuration

Ease of use in managing APIs on-prem and in the cloud

Need to install z/OS connect to access MF APIs

Developed a new Global Sales & Servicing Platform

I think the support for IBM products is superb.

The level of upfront support is not as easily accesible.

Developing IoT technologies with the IBM Cloud

Speed and Performance and Enterprise grade quslity of service

User Interface is cumborsome. Its not open source!

Exposing Legacy application functionality to business partners

Ability to do microservices and expose them as APIs.

Maturity to be enterprise ready and not easily deployBle

Expose services as APIs

Deploys in containers, UI is easy to use

upgrade is hard if you use AWS and have ICP professional

leveraging data

Integrated with Datapower and user-friendly

Unreliable and unstable when deployinmg in prod

Exposing APIs internally for mobile app

Easy to understand interface, capability.

Inability to validate LTPA Tokens in the APIConnect

API Management