Rethinking Cloud-Native Patterns on Kubernetes
summary
Introduces the OSS project Temporal as a resilience backing service with language SDKs that stores event history and activity results so apps replay predictable code and reconstitute state; the demo runs an order pipeline (payment, parallel email and shipping), the app process is killed and Kubernetes restarts it while retries implemented at the server continue, eventually succeeding; used in production by Snap, DoorDash, Airbnb, Netflix and OpenAI’s coding agent for multi-day workflows.
AI-written summary · about
chapters (9)
- 0:00Cloud-native patterns intro
- 1:24App architecture evolution
- 3:07Kubernetes resilience
- 5:39Traditional resilient patterns
- 9:10Temporal for resilience
- 13:08Temporal state management
- 19:30Temporal live demo
- 21:57Crash-proof execution demo
- 23:45Real-world Temporal use cases
related talks
35mBuild fault tolerant, distributed apps with Kubernetes and Temporal
26mMicroservices Madness: Application And Infrastructure Automation Using Temporal
26mTemporal: A Better Way to Build Modern Applications
50mThe end of event-based architectures? Orchestration with Temporal
30mOrchestrate Your Business Workflows with Temporal
33mLessons learned using Temporal to run Temporal Cloud
12mHow Affirm Uses Temporal as a Batch Data Plane
42mHow to build distributed systems in JavaScript