Story
Confluent
Origin EnergyOrigin Energy Adopts Confluent for Real-time Operations
Origin Energy, a utilities organization in Australia, uses Stream Governance from Confluent to support real-time operations for platform engineers.
Shared Stream Governance workspaces help Origin Energy keep real-time operations honest across teams.
“Inside Origin Energy, real-time operations used to depend on whoever still had the latest file.”
“Platform engineers needed a system that would still make sense after the original project team moved on.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Fewer stalled items because event streams has a clear owner |
| Productivity | Handoffs in real-time operations sit in a shared queue instead of a mailbox trail |
| Capability | New joiners can see how real-time operations actually runs |
Story
Inside Origin Energy, real-time operations used to depend on whoever still had the latest file. That pattern is common in utilities groups working out of Australia. Platform engineers needed a system that would still make sense after the original project team moved on.
Origin Energy uses Stream Governance from Confluent as the working layer for event streams. Confluent is the data streaming platform built around Apache Kafka, used to move events between applications in real time. The practical change is simple: real-time operations has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Origin Energy gets from Confluent is a durable place to run real-time operations and a way for platform engineers to see the same event streams at the same time.
