Story
1Password Uses Flink on Confluent for Event Streams
1Password, an information technology organization in Canada, uses Flink on Confluent from Confluent to support real-time operations for platform engineers.
Value results
| Category | Value result |
|---|---|
| Capability | Platform engineers work from the same Flink on Confluent record for event streams |
| Capability | Event streams can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for event streams |
Story
Inside 1Password, real-time operations used to depend on whoever still had the latest file. That pattern is common in information technology groups working out of Canada. Platform engineers needed a system that would still make sense after the original project team moved on.
1Password uses Flink on Confluent 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 1Password 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.