A Conversation with Platform Teams @ Replay 2026: Scaling Temporal Across the Enterprise
summary
Platform teams describe how Temporal moves from prototype to enterprise: successful rollouts use Temporal Cloud only with automated namespace and Okta onboarding via a Terraform provider automation and self-service portals, and teams measure adoption with 150 teams, ~800 users (Netflix), dozens at Redis, ~1,000 engineers federated at Apollo and ~15 teams at one retailer. Examples include long‑running workflows as dedicated services, Terraform executed by workflows, cross‑region failover demos that proved reliability, and the persistent obstacle of Kafka/BPM misconceptions.
AI-written summary · about
chapters (10)
- 0:00Introduction and panel setup
- 1:06Panelist introductions and context
- 8:29Platform teams' role in adoption
- 12:23Developer awareness and discovery
- 17:14Overcoming adoption obstacles
- 19:20Developer onboarding strategies
- 23:08Developer aha moments with Temporal
- 29:53Selling Temporal to leadership
- 35:54Metrics and leadership buy-in
- 37:59Closing remarks and career impact
related talks
27mFostering developer autonomy: Culture-driven platform engineering
22mThe challenges of Platform teams
46mBeyond DevOps: How and Why Companies Converge on Platform Models
44mPlatforms FTW!
26mLessons Learned from 7 years of Running Developer Platforms
22mOrganising a fast growing DevOps team a real life use case
25mOverwhelmed by Scale: How Product Thinking Fixes Platform Teams - Dominik Schmidle
21mDriving Platform Adoption: Embedded SRE