Microservices Madness: Application And Infrastructure Automation Using Temporal
summary
Claims a Concrete alternative: uses Temporal with Go workflows and activities deployed as Kubernetes workers, durable state survives worker failures and resumes execution, built e‑commerce example that parallelizes inventory and payment calls, retries with exponential backoff and compensation logic run in normal error handlers. Demonstrates scaling by changing activity concurrency or remove activity to a new worker and independently scale deployments, shows web UI and event history, runs about 200,000 workflows/day, and enables programmatic infra changes (ASG/pods) no YAML for infra.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:47Microservices are becoming unmanageable
- 2:48How did we get here? Oversimplified
- 5:40Reality is different
- 7:48Can we solve this?
- 8:43Better way
- 16:08Reliability
- 18:51Scalability
- 22:24Your application can Bring Its Own Infrastructure
- 23:25Other Use cases
related talks
26mRethinking Cloud-Native Patterns on Kubernetes
30mOrchestrate Your Business Workflows with Temporal
42mHow to build distributed systems in JavaScript
33mLessons learned using Temporal to run Temporal Cloud
26mTemporal: A Better Way to Build Modern Applications
50mThe end of event-based architectures? Orchestration with Temporal
23mDesigning a Workflow Engine From First Principles
01h 38mBuilding Reliable Distributed Systems