What We Learned Building Microservices
summary
Describes practical lessons from building a new product as microservices, focusing on operational changes: services became more dynamic, restarted frequently, and node counts grew exponentially. Discusses technologies and practices needed to manage that dynamism—service orchestration, monitoring, and deployment patterns—to keep many small interacting services stable.
AI-written summary · about
chapters (12)
- 0:00Start
- 7:59How micro should a microservice be?
- 10:59Requirements for a microservice
- 16:19Configuration
- 19:18How to decide?
- 20:47Our stack
- 22:42General recommendations
- 25:46Where is the complexity?
- 26:52Testing stages
- 28:04What have we tried?
- 30:52Service registry
- 32:47Consul Template
related talks
40mWhat I Learned Building a Microservices Architecture
45mMicroservices: A retrospective
01h 08mThrough Microservice Land with Node.js
49mMicroservices: An unexpected Journey
32mMicroservices: A retrospective
48mMicroservices in Production, Now What?
52mMicroservices: A Utopian Mystery
57m6 Lessons I Learned on My Journey from Monolith to Microservices
