Microservice specifics illustrated by an e‑commerce platform
summary
The talk analyzes microservice adoption in an e-commerce platform (example: Lamoda), describing risks discovered during the transition such as unwanted service coupling and other operational pitfalls, and how the team addressed them in place. It reports concrete benefits—time to market was halved—and explains how they retained control over a growing number of services while managing those specific risks.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:18Monolith limitations
- 11:51Transition to microservices
- 14:23Service boundaries
- 20:00Human factor challenges
- 27:07Versioning contracts
- 32:55Data storage transactions
- 37:15Business buy-in ROI
- 41:09Data integrity ownership
- 47:56Challenges pain points
- 49:45Q&A
related talks
45mE-commerce platform. Core build principles, problems and guidelines.
44mPragmatic Microservices
38mMicroservices, a bittersweet symphony
49mMicroservices: An unexpected Journey
54mThe Long Sad History of Microservices
32mMicroservices: A retrospective
42mHow to f*ck Up Your Development Team with Microservices
48mMicroservices in Production, Now What?
