At the OpenShift Commons Amsterdam gathering, the premier "Day zero" event for KubeCon + CloudNativeCon Europe 2026, the energy was electric, with a session that perfectly captures the spirit of cloud-native transformation.Joerg Meyer, Software Solution Architect at Diebold Nixdorf, took the stage to deliver a compelling presentation titled, "Diebold Nixdorf Breaks the Shackles of Legacy Payments Infrastructure." Meyer shared how this global leader in banking and retail technology is moving away from the rigid constraints of the past to build a high-availability, future-ready payments platform.
Figure 1. Joerg Meyer, Software Solution Architect at Diebold NixdorfThe weight of legacy: Banking in a monolithic worldYou likely interact with Diebold Nixdorf daily without realizing it. Whether you are withdrawing cash from an ATM or using a credit card at a retail desk, there is a high probability their software or hardware is powering that transaction.Historically, these systems were built on "bending metal"—the physical ATMs and cash machines. However, as Meyer explained, the software backend was often a "mainframe story":Monolithic and rigid: Applications were heavy, expensive, and tied to specialized hardware.Scaling challenges: Growing the business required vertically scaling on costly proprietary machines.Maintenance hurdles: Updating a system often meant significant downtime, as "swinging" traffic from an old system to a new one frequently caused service interruptions.The Java sunset: Many banking organizations are currently "stuck" using older versions of Java (like Java 8) due to the sunsetting of traditional Java enterprise servers, creating both security and operational risks.The vision: VynamicⓇ PaymentsTo address these challenges, Diebold Nixdorf developed Vynamic Payments. This wasn't just a software update, it was a total architectural shift using domain-driven design to break functionality into "bounded contexts."By moving to a microservices architecture, they decoupled critical functions like cryptography, card handling, and account limits. This allows them to update a single payment network—like Mastercard or Visa—without affecting the rest of the application.The solution: Why Red Hat OpenShift?When looking for a runtime environment to execute this vision, Meyer’s team chose OpenShift as their "stable platform." By lifting the application to a higher level of abstraction, they achieved several critical goals:Cloud agnostic: OpenShift allows Diebold Nixdorf to run anywhere—AWS, Google Cloud, Azure, or on-premise. They no longer care about the underlying physical layer.Zero downtime with blue-green deployments: They can now "change the horse while riding it." By installing a new release on a "green" system while the "blue" system is live, they can partially swing traffic over for testing before committing to the full fleet. If an issue arises, they simply swing back to the blue system with zero non-availability for the customer.Active-active high availability: Using a Kafka-based database replication, they can run 2 data centers independently. In a powerful demonstration, Meyer showed that even if an entire AWS region fails, the system automatically scales and keeps the business running without losing transaction frequency.Results: Stability at 50,000 feetBy using OpenShift operators, Diebold Nixdorf has integrated third-party dependencies like Kafka and databases directly into the platform, drastically reducing operational overhead.As Meyer put it, they are now, "flying at a level of 50,000 feet." They have moved from being a company that "bends metal" to one that provides a comprehensive application innovation platform for the future of global finance.See the transformation in actionWant to see the technical deep dive and the live failover demonstration?Watch the full session from OpenShift Commons Amsterdam here.Ready to break the shackles of your legacy infrastructure? Learn more about how Red Hat OpenShift can power your most critical applications.
