Supercharging Cloud Orchestration with Temporal Open Source
summary
Capital One replaces choreographed Lambdas with a durable execution platform built on self-hosted Temporal on Fargate, fronted by an NLB, using RDS Postgres + S3 archival and EFS for dynamic configs, OpenTelemetry sidecars, and a custom JWT/OIDC authorizer for namespace-based access. The platform runs multi-tenant provisioning, drives observability and rollback-safety, and speeds delivery from months to days; deployment costs include auth complexity, DB migration changes, and compute-layer replication. Outcome: production use since early 2024 with 50+ infrastructure capabilities, 100+ contributors and measurable developer velocity and standardization gains.
AI-written summary · about
chapters (9)
- 0:00Introduction and speakers
- 1:05Capital One's cloud transformation
- 7:48From static to durable execution
- 9:12Temporal open source deployment
- 17:16Authorization and security setup
- 19:24Challenges in integration
- 23:58Payoffs and business impact
- 28:49Key takeaways and best practices
- 38:59Closing and acknowledgments
related talks
30mOrchestrate Your Business Workflows with Temporal
26mRethinking Cloud-Native Patterns on Kubernetes
26mTemporal: A Better Way to Build Modern Applications
50mThe end of event-based architectures? Orchestration with Temporal
26mMicroservices Madness: Application And Infrastructure Automation Using Temporal
46mArchitecting for Success and Runway
44mOrchestrate Your Business Workflows with Temporal.io
38mOS-Climate & SIG-SRE: Benefiting from the Operate First Community Cloud