The Evolution of Microservice Architecture
summary
Evolution of Twilio’s Conversations API microservice architecture: the talk describes why and how the team refactored service boundaries—when they split services and when they merged multiple services into one—covering drivers for those changes, the approaches used to decompose services, and the resulting architecture and how it enables implementing new product features.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:07Twilio Conversations overview
- 4:46Evolving microservices
- 8:45Architecture challenges
- 13:44Migration prerequisites
- 16:15Synchronous vs event-driven
- 18:04Event-driven types
- 21:01Domain-based splits
- 25:04Functionality splits
- 27:36Consolidating services
- 32:18Results and benefits
- 34:29Migration trade-offs
- 36:18Q&A
- 38:32Q&A: Service growth
- 41:47Q&A: Terraform and IaC
- 43:34Q&A: Multi-region availability
- 44:38Q&A: Testing and DevOps
- 46:25Closing
related talks
37mEvolutionary Architecture & Microservices
24mPatterns of Evolution from Monolith to Microservices
32mMicroservices: A retrospective
14mSAG Expert Interview #05: The Evolution of Microservices
40mWhat I Learned Building a Microservices Architecture
39mWelcome To The Era Of Microservices
54mThe Long Sad History of Microservices
01h 14mThe Philosophy of Microservice Design with ServiceTalk.io