What lies beyond microservice architecture? From Microservices to Distributed Platform Architecture
summary
iFood describes moving the Payout Team from monolith → microservices → a distributed platform by measuring domain growth with a Big‑O style complexity chart and reorganizing teams into platform “neighborhoods.” concrete moves: split into ~60 services for one business unit, scale company‑wide to 3,000 microservices, introduce clear platform boundaries, prefer public channels and a message broker/eventing approach, invest in developer tooling and billing per‑platform. result: reduced ad‑hoc cross‑service coupling and clearer ownership, at the cost of higher infra and coordination effort.
AI-written summary · about
chapters (10)
- 0:00Beyond microservices intro
- 3:37Software as living system
- 7:39Monolith to microservices
- 11:32Why complexity grows
- 14:24Microservice challenges
- 19:00Right architecture?
- 20:26Distributed platform intro
- 25:50Platforms like city blocks
- 27:13Detecting bad smells
- 28:19Q&A
related talks
42mFrom Monolith to Microservices: The Evolution of a Banking Platform
52mWhat Does a Good Microservice Architecture Look Like?
37mEvolutionary Architecture & Microservices
49mFrom Microservices to Migroservices
44mA Software Engineer's Journey Through Microservices Data Sharing
48mService Oriented Architecture - Slice and Dice
55mMicroservices, Where Did It All Go Wrong
01h 00mMicroservices, Where Did It All Go Wrong?