Microservices are the answer - but what is the question?
summary
Three rebuilds of microservice architectures for major companies lead to concrete rules: use Kubernetes, Prometheus, Grafana, Kibana for orchestration, metrics and logs; prefer JWT and Redis for session/state; pick a single orchestrator microservice to coordinate distributed operations, order easy-to-rollback actions first and implement draft statuses for compensations. Microservices win for large, stateless, fast-changing workloads but cost RAM/CPU, complicate debugging and transactions, and often demand CI/CD and correlation IDs to make production support feasible.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:52Microservices 101
- 5:45Orchestrator 101
- 7:51DevOps 101
- 12:07Microservice Design
- 14:16Think Generic
- 16:27Microservices Design
- 20:14Session
- 26:08Transactions with legacy systems
- 30:40Microservice vs Monolith
- 31:36Better request tracking
- 32:35Orchestrators nowadays
- 33:41Spring as orchestrator
