Microservices: 5 things I wish I'd known
summary
Five concrete lessons: treat services as cattle with health and deep checks and make them discardable; keep one repo one build and push an empty shell to production early; expect lots of deployments and aim under ~50 minutes from build to prod using AWS CloudFormation and Docker; test with WireMock/spring profiles or contract tests and add semantic smoke checks; secure service-to-service calls with JWT/ASAP; run-your-own teams, aggregate logs (Splunk/ELK), use circuit breakers and Zipkin tracing.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:43Why Microservices
- 2:33Issues with Microservices
- 6:10Responsibility
- 10:38Service characteristics
- 12:59Separation of conflict
- 19:53Testing
- 23:11Three solutions
- 29:35Failure is imminent
- 34:37Wrap up
related talks
44mMicroservices: 5 things I wish I'd known
45mBuilding and evolving microservices: lessons from the frontlines
52mMicroservices: A Utopian Mystery
45mMicroservices: A retrospective
52mSurviving in a Microservices Team
57mEmbracing Microservices
30mHow to Fail at Building Modern Microservices
26mCreating a scalable ecosystem of Microservices