Service Oriented Architecture - Slice and Dice
summary
Argues that microservices are an implementation style within SOA and decisions must be domain-first, not fad-driven. Cites Amazon Prime Videos, Netflix and isto control plane / STOD as real pivots from microservices back to monoliths, and names segment and vision as similar cases. Breaks architectures into monolith, microservices, microrends, BFFs and experience APIs, stresses benefits, costs and enablers, and reports a working self-service platform at Bunnings that lets teams scale (30 → 150) while warning about hidden complexity.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:29SOA definition and history
- 10:00Monoliths vs microservices
- 17:50Hybrid architectures
- 21:42Microreact and frontend patterns
- 26:21Backend for frontends
- 32:05Domain services
- 35:56Key takeaways
- 44:08Choosing patterns wisely
- 45:53Q&A
related talks
01h 00mService Oriented Architecture for Robust & Scalable Systems
49mMicroservices: An unexpected Journey
57mSOA lessons learnt (OR Microservices done better)
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
50mEmbracing Microservices
52mMicroservices & the Inverse Conway Maneuvre
01h 02mDesigning Microservices
14mSAG Expert Interview #05: The Evolution of Microservices