Azure API Management vs. SAP Integration Suite

The range of policies that enable the APIs to loosely couple it with security, rate limit, retry, etc. are good. We can easily tie authentication mechanisms to external and other internal services without having to modify the backend.

Incentivized

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.

• Management of APIs
• Security of the API through Azure AD, AD B2C etc.
• Providing an outer layer through APIs

• 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

• Cost - the upfront cost is a bit restrictive. I've been told it is because there are a few underlying VMs that are running this service. So if you're just starting out with API management, it can be an expensive proposition. Value increases as you add additional APIs. If you're using Azure B2C for the developer portal, you'll require Standard or Premium since they support AAD integration.
• Security granularity - at time of writing, APIM doesn't support breaking out operations to products. For example, if you have an API that has a GET and a POST operation, and you want the POST operation to require a different subscription. There is a work around, but it makes management a bit messy.
• Developer and Publisher portal - it's a little weird. Microsoft hasn't migrated all the publisher portal functionality into the "native" Azure portal. So some of it feels a little weird - especially when working with the content management side of things for the developer portal.
• Scaling - while it's easy to scale up, the cost of APIM ramps up very quickly. Standard -> Premium is a 4x jump.

Incentivized

• Could be even more business friendly with programming language abstracted
• Ability to simulate the integration flow instead of a real run
• Have some kind of an AI-assistant suggesting the optimal design of an integration flow as it's being built (best practice assistant)

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 is a user-friendly platform that enables fast setup for new subaccounts, launchpad and applications.

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

Azure APIM vs Amazon API Gateway:

1) Azure APIM was a complete package that included a developer portal.

2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.

3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway.

Incentivized

We used to have a in house application in Camel and Karaf as a middleware, and after we migrate to S4HANNA we decide to give a try and move to the cloud with SAP Integration Suite, knowing the capabilities and the needs that we have in the company and the projects that were running on premise in our middleware.

Incentivized

• It’s really pay as you go, so it's not that costly to get in and try it out. There’s no expensive client to buy and manage, but you do need to stay on top of the rapidly changing Azure environment to be sure you upgrade or adjust when needed.
• It’s not great having more than one API tool, but it’s ok to spread out your work, as you always want the right tool for the right job. For example, if you are a Salesforce-heavy organization, I’d go with Mule over Azure.
• It was easy getting an external consultant access to the tool to build their own API for a project they were working on for us.

Incentivized

• Ability to have multiple integrations across different SAP systems or modules and be able to actively monitor in one place
• APIs already exist for the different fields in SAP products and are easy to locate
• Can set email notifications to aid with monitoring and alert business process owners of issues

Incentivized