Kubernetes alone does not make an integration platform

At first glance, the approach seems simple. The integration logic runs in containers on a Kubernetes platform. In practice, however, it quickly becomes clear that Kubernetes is merely the foundation. The real effort comes from the requirements that must be met to ensure the productive operation of such an environment.

This is where many SAP customers encounter a subject area that is new to them. Integration teams often have many years of experience with traditional SAP technologies, middleware, and process integration. In contrast, their knowledge of Kubernetes, container operations, service mesh, automation, or cloud-native security is often limited. As a result, the implementation of the Edge Integration Cell becomes both an infrastructure project and a skills development initiative.

Often Underestimated: Sizing

One of the topics that is often underestimated is proper platform sizing. While Kubernetes environments can, in principle, be scaled flexibly, the reality of large enterprise environments is often quite different. Additional resources must be procured, approved, and integrated into existing operational processes. Errors in sizing and dimensioning can therefore have a significant impact on schedules and costs.

Equally important is choosing a platform that largely automates operations. Identity management, network functions, monitoring, logging, security mechanisms, container registries, and lifecycle management must work together reliably. Integrating and operating these components individually increases complexity and operational overhead. So-called “Day 2 operations” also deserve attention. Issues such as backup and restore, disaster recovery, platform upgrades, and the management of Kubernetes versions are often treated as secondary priorities in many projects. Under no circumstances should companies wait until after deployment to consider restart and recovery scenarios.

In addition to workload consolidation, the ability to run different applications on a shared infrastructure is becoming increasingly important. Red Hat OpenShift serves as a universal application platform for this purpose. As part of the S/4 transformation and Clean Core initiatives, side-by-side extensions can be developed as containerized applications and securely connected to S/4 via standard OData APIs. Automation, the Developer Console, and serverless computing reduce development times. Multi-tenancy and hybrid operating models lay the foundation for resilient and sovereign IT platforms.

Security first

At the same time, security requirements are increasing. Today, integration platforms often serve as the central communication hub between SAP systems, cloud services, and third-party applications. Even connecting to an on-premises AI solution such as Red Hat OpenShift AI is now possible using SAP EIC. Consequently, the requirements for isolation, access control, runtime monitoring, and the detection of suspicious activities are correspondingly high. Modern security mechanisms must therefore be an integral part of the architecture from the very beginning. The Edge Integration Cell is just a harbinger of a larger trend.

SAP is increasingly relying on container technologies and Kubernetes-based operating models. At the same time, many companies are modernizing their applications according to cloud-native principles and developing new functions outside the core ERP system. This is giving rise to platforms where application modernization, integration, and—in the future—AI workloads converge. The introduction of the Edge Integration Cell should therefore not be viewed solely as a successor project to PI or PO. Rather, it marks the beginning of a new generation of SAP infrastructures.

To the partner entry: