Microservices – Sean Smith
summary
Gilt Groupe moves from a monolith to a service mesh and reports concrete results: 250 microservices in production, an average of 50 successful deploys every day, and a broken Commons library with about 70 instances of Commons that forces a refactor into smaller libraries. The team builds an api doc generator that produces zero‑dependency clients (Play, Ruby, Scala) to drive API‑first development; a waitlist system with six services causes a mobile notification bug that loses revenue, then gets simplified and consolidated.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:30Driving forces behind gilt's emergent architecture
- 6:24Example: 'commons'
- 6:56Gilt Commons
- 9:26Client/Server/Core
- 11:21How To Avoid
- 11:39Lightweight Clients
- 13:22Apidoc Advantages
- 16:18Example: Waitlist
- 19:43Problems
- 21:28Antipatterns
- 22:38Recap
related talks
35mMicroservices: A Tale of 3 Heroes
01h 01mMicroservices Gone Wrong
43mGo micro with Microservices
26mFighting the Good Fight at the Hot Gates of Micro-Services
24mMicroservices in Practice
47mMicroservices? Monoliths? An Annoying Discussion!
44mMicroservices - How to create problems by solving problems?
44mMicroservices: 5 things I wish I'd known