I had microservices and I didn’t know
summary
A company grows from two people to ~30–60 over six to seven years and discovers its backend is actually a set of microservices: five or six web apps (a player server, a tournament server, a CMS, a moderated live‑tweet feed) each mapped to a bounded context and implemented independently, using ASP.NET, NuGet and later Docker containers for packaging. Claim: microservices emerge organically for productivity and operational needs, not because of hype; the setup works in production for live tournaments.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:48Microservices
- 4:10Failed
- 5:18Worst Microservices
- 7:50Microservices Definition
- 13:19Why microservices
- 17:07Blocks
- 25:43How to get there
- 26:27Domain Driven Design
- 28:54Bounded Context
- 40:40Summary
- 51:43Conclusion
related talks
52mI Have a Microservices Architecture and I Didn't Know.
01h 01mMicroservices Gone Wrong
48mThirty months of microservices
32mMicroservices Orchestration with
56mModular Monolith and the Prisoner of Microdisservices
23mMicroservices – Sean Smith
35mSeven years with microservices: a critical review
23mMICROSERVICES ARCHITECTURE AS IF YOU MEANT IT