SAP Integration Suite vs. WSO2 API Manager

The case of the SAP Integration Suite shows outstanding capability in handling huge data, and especially when handling corporate portfolio data with multiple owners. But we have noticed that in the cases of moving data from the older banking system, it is necessary to further refine the system. It does an excellent job of the current credit scoring.

It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?

Incentivized

• Broad Connectivity: SAP Integration Suite excels in connecting diverse systems, including SAP and non-SAP applications, databases, and third-party services.
• Pre-built Integrations and Templates:The suite provides a library of pre-built integrations and templates for common business scenarios.
• User-Friendly Design Tools:
• API Management:

Incentivized

• Authentication based on OAuth 2.0 and HTTP Basic Authentication.
• Rate Limiting applied at different levels like Subscriber, API, Resource and Backend.
• Monitoring by exporting the metrics in Prometheus and traces in Jaeger.
• Mediation to perform transformation, orchestration etc.

Incentivized

• Provide more pre-built integrations to use within SuccessFactors or other modules instead of everything having to be custom built
• Support is unable to provide advice on custom builds so you often have to engage a 3rd party partner
• Works best when you have the functional and technical teams working together. Otherwise, the system is too technical for a functional user to create integration and a technical user not always understand the functional perspective

Incentivized

• Better QA testing prior to releases rollout
• Better support needed

Incentivized

SAP Integration Suite is very helpful to us in many ways to manage purchase procedures, stocks, and data of vendors and suppliers. Also, it helps to manage data for service providers. SAP Integration Suite has the tool to conduct training and evaluation. Unique features like the cloud can provide access from any place and by any device is very helpful.

Incentivized

It's very easy to use and configure.

Incentivized

Support is hard to reach and takes a long time to get a response.

Incentivized

Work with an SAP implementation partner, if possible.

Incentivized

SAP Integration Suite was already part of our SAP stack, part of Business Technology Platform, with out-of-the-box integration with S/4 HANA transactional and ERP system that we are using as our main back-end. Thus, we are achieving significant Total Cost Optimization benefits or running both solutions on the same platform, hosted on Azure cloud.

Incentivized

Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.

Incentivized

• In the long run will enable us to undeploy our on premise solution
• As long as integration suite doesn't support all capabilities PO has complete migration is hard
• Will probably be cheaper than our on premise solution when we are completely migrated

Incentivized

• We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
• Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
• Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.

Incentivized