IBM Z transaction events are ready for real-time enterprise use

At IBM Think 2026, Ric Lewis, IBM SVP of Infrastructure, made a point that captures a broader shift in enterprise architecture: “Data is either a gold mine or a landfill—and architecture is what determines which.” Jay Kreps, co-founder of Confluent, framed the same issue from an engineering perspective: “By the time you get your data, the customer’s gone.”

For enterprises that rely on IBM Z®, that observation is especially relevant. IBM Z runs critical transactions and operational flows for many large organizations. Payments, trades, claims and regulated business processes already execute on IBM Z with the trust, resilience, integrity and security those environments are designed to provide. The transaction events created in those systems are already central to business operations.

The question now is how those events are used across the rest of the enterprise. Fraud platforms, compliance workflows, analytics systems and AI models increasingly depend on real-time inputs. They need events that are current, structured and governed from the moment they enter enterprise use.

The value of a business event is highest when it is still close to the transaction that produced it. That stage is where context is richest, governance is clearest and timing is most critical.

This proximity matters in every enterprise environment, but especially on IBM Z. IBM Z is already the system of record and execution for many of the transactions with the greatest operational impact. The events created there directly represent business activity the enterprise already depends on.

This direct connection to business activity is what makes origin matter. Real-time enterprise use works best when governance begins early, while the event is still close to the system that created it. That gives downstream consumers more current signals, a more consistent structure and a stronger basis for action.

Confluent Platform is an enterprise data streaming platform built around Kafka and trusted by 40% of the Fortune 500. It is now certified on IBM Linux on Z and LinuxONE and runs natively on s390x. In an IBM Z environment, that means transaction events created on IBM Z can be used as governed real-time signals at enterprise scale.

Its core capabilities matter directly in that setting. Kafka carries transaction events into enterprise streaming flows for multiple consumers. Schema Registry establishes policy and structural consistency at publication. Apache Flink enables filtering, enrichment and correlation close to the event stream. Together, those capabilities support governed reuse of IBM Z transaction events across the enterprise.

Connectivity is equally important. z/OS applications and data, IBM Linux on Z workloads and enterprise-wide systems can all participate in the same real-time streaming model. IBM MQ, IBM Open Enterprise SDK for Apache Kafka, IBM Z Digital Integration Hub and IBM Data Gate for Confluent provide IBM Z-specific paths into that flow. The broader Confluent ecosystem extends those flows to other enterprise consumers and platforms.

The result is not a new rationale for IBM Z. It is a broader and more consistent way to use IBM Z transaction events in real time.

The practical effect is clearest in operating models that already depend on current transaction signals.

•    Fraud detection. IBM Z Digital Integration Hub can surface business context from live transaction flows, while IBM Data Gate for Confluent streams Db2® for z/OS changes into downstream analytics and AI environments. Confluent Platform enables those inputs to be used as governed real-time signals for fraud and risk systems that need to act quickly.
•    Regulatory compliance. Compliance workflows depend on traceability, consistency and control. When schema policies are established at publication and governance begins closer to the originating event, downstream compliance and audit processes work from a stronger event foundation.
•    Analytics and AI. AI and analytics systems depend on data that is current, well-structured and governed. When IBM Z transaction events enter enterprise use through a governed streaming model, those downstream systems receive real-time inputs with clearer provenance and more immediate operational relevance.

IBM Z and LinuxONE provide the capabilities enterprises already expect for business-critical operations: trust, resilience, security and scale. That matters when real-time event consumption expands beyond a single application or workflow and becomes part of a shared enterprise infrastructure.

Hardware-backed encryption supports secure processing of sensitive event data. LinuxONE supports scale without introducing unnecessary operational fragmentation. A governed streaming model on IBM Linux on Z and LinuxONE creates a more consistent way for multiple teams and consumers to use the same event signals across the enterprise.

The broader significance is that IBM Z runs the business. Confluent Platform enables those business events to be used safely and consistently in real time, across more consumers, more workflows and more enterprise decisions.