Event Processing at Optum, the Cloud Events Way
summary
Optum runs an on‑prem serverless platform with 1,000+ functions used by 500+ developers and processes ~1 trillion transactions yearly; the engineering claim is that adopting CloudEvents headers plus knative broker lets diverse sources (Kafka, S3, FTP, GraphQL, device SDKs) publish to a single event mesh and triggers route by event type without inspecting payloads. Demos show end‑to‑end builds with ko + kn (Go service → container → HTTPS URL) and use cases: Infrastructure360 ingesting 40 sources, ETL eligibility pipelines, and multi‑vendor IoT ingestion.
AI-written summary · about
chapters (6)
related talks
28mCloudEvents - A First Step Towards Serverless Interop
41mOpen Standards for Building Event-Driven Applications in the Cloud
37mBuilding Event-driven Apps at Scale
42mReal-Life Implementations of Event-Driven Processes
27mEvent-driven Digital Transformation
45mBuilding Event-driven Serverless Applications
26mEvent Driven APIs
31mUsing Telemetry in Cloud Native Applications