Microservice of the brain. Recipes for quality
summary
Describes how SberCloud reworked application design when moving to microservices to avoid the common pitfalls: exploding dependencies, accidental microservice monoliths, and quality drift. Covers concrete practices for performance optimizations, maintaining data consistency and reducing bus-factor risk, and engineering processes for monitoring and ensuring overall quality.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:17Frontend microservice architecture
- 7:39When microfrontends are needed
- 12:40Tech stack for microfrontends
- 18:43Slicing microservices correctly
- 27:04Microservice development standards
- 36:50Painless change deployment
- 41:12Boilerplates and shared libraries
- 45:51Service creation templates
- 46:58Dependency management in 80+ services
- 49:07Debugging and testing microservices
- 51:39Team structure for microservices
- 54:27Summary & Q&A
related talks
38mMicroservices, a bittersweet symphony
52mMicroservices: A Utopian Mystery
54mThe Long Sad History of Microservices
57mBuilding Microservice Architectures
43mGo micro with Microservices
45mMicroservices: A retrospective
43mPanel: Microservices, Where Did It All Go Wrong
52mWhat Does a Good Microservice Architecture Look Like?
