Surviving Microservices
summary
Starts with a small MVP that typically takes nine months for an MVP and about ten services to prove patterns: API contract-first with OpenAPI, CI/CD pipelines, local Docker/Compose, and an image registry workflow that never uses latest in prod. Design embraces CQRS/event messaging for eventual consistency, message-based audit/history, per-service data stores, distributed tracing and ELK/Splunk logs, canary/feature-flag rollouts, and readiness drills for clusters and thousands of containers to make independent deploys workable.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:55Play to Win
- 4:58Why Microservices
- 9:17Large Companies
- 10:01Design Phase
- 23:36Getting Comfortable
- 26:06Using Messaging
- 28:56Design is Hard
- 32:46Local Development
- 36:46No Code Sharing
- 42:56Build Dashboards
- 44:46Unit Testing
- 46:06The Most Important Thing
- 47:16Its a Team Effort
- 49:31Its a FullTime Job
related talks
57mSurviving Microservices
45mMicroservices: A retrospective
45mContinuously delivering containerized, highly available microservices
25mMaking microservices a behaviour not a buzzword
52mI Have a Microservices Architecture and I Didn't Know.
28mSurviving in a Microservices Environment
24mPatterns of Evolution from Monolith to Microservices
01h 01mMicroservices Gone Wrong