I Have a Microservices Architecture and I Didn't Know.
summary
Argues that many systems accidentally become microservices and gives a concrete case: a startup grows into six distinct MVC applications (API server, player service, CMS, tournament server, etc.) that communicate by APIs and sometimes a shared database, use docker and containers where helpful, and rely on NuGet for reuse while Visual Studio struggles with huge solutions. Claim is that this incremental build delivers measurable productivity and replaceability and that the approach actually works though tradeoffs around shared schemas and deployment remain.
AI-written summary · about
chapters (10)
- 0:00Introduction to microservices
- 4:20Defining microservices
- 10:25Service-oriented architecture
- 14:35System architecture design
- 18:54Implementation considerations
- 23:11Breaking down the monolith
- 27:05Connectivity and communication
- 30:40Domain-driven design
- 35:56Context mapping
- 42:22Conclusion and Q&A
related talks
55mI had microservices and I didn’t know
52mWhat Does a Good Microservice Architecture Look Like?
57mEmbracing Microservices
55mMicroservices, Where Did It All Go Wrong
01h 02mDesigning Microservices
48mIT Architecture : All your micro-services are wrong PERIOD!
38mMicroservices, a bittersweet symphony
45mMicroservices: A retrospective