Kong Konnect vs. SAP Integration Suite

Using Kong [Konnect]'s declarative settings, a user may control traffic, automate deployment, and maintain container-based software after it's deployed. In addition, it handles the whole lifecycle of service management. Installation, management, and operation of Kong [Konnects]'s cloud-native connection runtimes may be performed in any cloud or Kubernetes provider environment, as well as on-premises environments. In order to optimise their services and transactions, users may keep track of their services and transactions in real-time via real-time monitoring.

Incentivized

Good at: 1. Integrations with in SAP applications, especially with event based triggers 2. Can be integrated very well with other BTP services to attain Batch processing and store credentials 3. Supports many authentication models Improvements: 1. No version history available compared to as it is available in S4HANA 2. Need a lot of improvement in git hub connections

Incentivized

• Application orchestration
• Error tracing
• Analyzing traffic
• Load balancing

Incentivized

• The extensive catalog of pre package integrations that have in the discovery center. That allows developers to find solutions that can fit the needs.
• Monitor of the integrations and api deployed.
• API management has been for us a very usefull tool inside integration suite, to be able to have the API Hub with the documentation of our apis.

Incentivized

• Community support
• Sample projects for easy integration

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

It is in place, our system integrators are familiar with it, and it fits into the ecosystem. A better user interface, flow build and debugging experience would see it grow, many technical staff do not enjoy using it for this reason, however it is quite capable and powerful behind this one shortcoming.

Incentivized

The user interface is messy and not intuitive. It has a steep learning curve, and flows developed around are easy to make a mess with layout and can be difficult to follow. The debugging is also quite difficult, it takes some time to figure out how to follow the flow and examine data. Error handling is also difficult and not intuitive, it is better to let some errors leak and monitor through ALM.

Incentivized

The support for SAP Integration Suite is satisfactory. We leverage SAP support through our manage services partner. So far, we have not had many major issues. One concern, to make our rating a ten, would be turnaround time on high priority incidents. SAP Integration Suite drives our key business functions forward. Without a reasonable service level agreement on turnaround, we sometimes find us running into issues running pay, etc.

Incentivized

Work with an SAP implementation partner, if possible.

Incentivized

Before deploying SAP Integration Suite, we assessed Oracle Financial Services Analytics and IBM Risk Analytics. While Oracle had proved its mettle in the exceptional database support and IBM in presenting risk model tools, SAP Integration Suite overwhelmed others by being effortlessly integrated with our existing banking framework.

• Increased application efficiency
• Reduced system downtown
• Significantly improved error resolution

Incentivized

• Positive impact would be availability of pre-defined integration content via templates.
• One can re-use a template as a starting point to modify and adopt to client-specific integration flow.
• Availability of adaptors and connectors, making it easier to piece together the integration flow.

Incentivized