Tech odyssey: The epic saga of a mega migration to temporal
summary
The team migrates Grab Unlimited from a brittle legacy to Temporal, using a focused tiger team (two backend, one QA) and a staged per-country rollout across seven markets, completing design and rollout in about four months including holidays. Operational results show 90% reduction in incidents and no severity one incidents at rollout, with tradeoffs: steep Temporal learning curve, onboarding gaps, and QA burnout. The collateral: reduced maintenance cost, faster feature routing, and a blog post with system-level details coming on Grab Engineering.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:30Legacy system failures
- 5:18System failing interviews
- 7:01Planning principles
- 9:54Tiger team building
- 11:17Design objectives and choosing Temporal
- 14:29Timeline and process
- 15:55Zero severity-one rollout
- 16:16New tech challenges
- 17:20Testing pitfalls solved
- 18:26Onboarding gaps
- 19:31Regional rollout fixes
- 20:34Team morale struggles
- 21:38Problem-solving moments
- 22:00Migration outcomes
related talks
26mTemporal: A Better Way to Build Modern Applications
38mHow to Leverage Temporal for Agentic Orchestration and Workflows
50mThe end of event-based architectures? Orchestration with Temporal
44mOrchestrate Your Business Workflows with Temporal.io
46mThe End of Event-Based Architectures? Orchestration with Temporal
47mBuilding an OMS with Temporal: From Zero to Tens of Thousands of Orders per Day
28mDurable Code Execution With Temporal
26mRebuilding at scale: A CTO’s journey in a high-growth fintech