IBM API Connect vs. WSO2 API Manager

Overall, it can be stated that IBM API Connect has many benefits and can easily manage complicated integrations. The platform performs best in large environments, especially where microservices and processing of multiple API dependencies are required. On average, we have processed thousands of API calls within a second with good response time.

Incentivized

WSO2 is a unique product that provides pre-integrated components like Gateway, Integrator, identity management, etc. Hence it is best suited when the requirement is not just only publish the APIs but also to secure and transform the APIs. WSO2 can be an overhead if only Gateway is required, as there are other very lightweight gateways available in the market.

Incentivized

• API discovery feature is very helpful to allow us to scope the work required before diving into things.
• The ability to set permissions and rulesets at a user level is essential to restrict access to specific datasets.
• Ability for external users (those from outside our organisation) to leverage the API in more restrictive manner.

Incentivized

• API Security
• API Transformation
• API Monetization

Incentivized

• That being stated, every thing you own will have both positive and negative aspects to its use. It can be perplexing at times, particularly when navigating between different functions.
• However, based on my usage of this application up until this point, I've discovered that the only time it lags is when it's downloading updates. Otherwise, it's excellent to utilise for all other customs.

Incentivized

• Installation of this product is a hell. You need to be an expert to get this running together with WSO2 Analytics. It uses a really confusing method of "port + 1" to connect extra products. I guess this was meant to provide a handy way to add new WSO2 products. In reality you'll need to scroll through numerous config files to set this straight. If you use this out of the box, everything will work all right. But the moment you add SSL certificates, DNS names and you'll need special ports to configure your firewall, this product becomes unmaintainable.
• The "Store" provides a nice way to group API's. However, the "Publisher" does not... if you have more than 30 API's searching for API's becomes really annoying.
• The number of configs in this product is huge. As a developer myself, I've never seen (and definitely never created) a product that needed that much config files. Installation and maintenance of products should be stupidly simple, since no developer nor infrastructure person wants to learn something that "just" needs to be a tool.. opposed to being a whole new area of expertise. After using WSO2 API Manager for a while, we wanted to change the admin password... this should be simple enough, like just change the password in "Carbon." But nope. The whole WSO2 environment crashed. We just gave up. Too dangerous.
• Why so many different "products"? Publisher, Store, Carbon, and numerous hidden interfaces. Analytics, ESB whatever... No wonder there are so many config files and port issues. Make it simple!!!

Incentivized

IBM API Connect may be less appropriate for small-scale projects with minimal API management requirements, where simpler and more cost-effective solutions suffice. Organizations lacking the necessary technical expertise or resources to harness its full potential may face implementation challenges. In static environments with infrequent API changes or limited developer engagement, the platform's comprehensive features may be excessive for the task at hand.

Incentivized

Our decision to adopt IBM API Connect was driven by its comprehensive end-to-end API lifecycle management, which proved to be exceptionally well-suited to our B2B, Open Banking, and multi-fintech integration requirements. When compared with other solutions, API Connect stood out for its ability to externalize and govern APIs at scale, while offering enterprise-grade capabilities critical for our regulated environment. IBM App Connect serves as our internal integration middleware, focused on backend orchestration and data transformation. IBM watsonx acts as a complementary AI and data platform for exposing intelligent services especially with the code assistant functionality, it is API Connect that provides the crucial layer for external API exposure, management, and monetization. IBM DataPower is an incredibly secure and performant runtime, and lacks key enterprise features such as developer engagement, full API governance, and analytics. API Connect fills that gap seamlessly, offering a unified, secure, and scalable API management experience.

Nevatech Sentinet: The easiest API Manager available. No knowledge of how the product works internally needed! It works with C# (not java... with all it's config files... really? Java developers?). Great way to categorize API's into groups (domains). All of which is drama in WSO2. But Sentinel is really expensive... Mulesoft: Nice and clean. Again, no expert knowledge needed of how the product works internally. Like using word... or any other application, except WSO2. Have java developers never heard of exposing configurations through a user inyterface?? Mulesoft, however is really expensive. Azure: Not cheap!! And a chaotic interface too. But it pays! If you have a Microsoft account already, this is your next step. We chose WSO2 4 years ago because it was free... but we're moving to azure now. And we're very happy with that decision.

Incentivized

• It has decreased the average development time of an API by 15%.
• It has simplified the monitoring and tracking of development, keeping it simple and in one place.
• It has reduced the time wasted looking for information; it has reduced the mail loop sharing status and questions.

Incentivized

• Positive impact on continuity and API standardization.

Incentivized