Surviving in a Microservices Team
summary
Checklist of concrete practices and failure modes: set up centralized logging with ELK (or outsource to Loggly) and metrics/tracing via Zipkin; automate builds and deploys with Jenkins pipelines and enforce quality gates with SonarQube; prefer RabbitMQ (or Kafka) with a global event log to bootstrap new services; avoid sharing domain code between services, use service templates, and aim for continuous delivery; implement dead-letter queues and circuit breakers — about 70% of production bugs come from mishandled messages.
AI-written summary · about
chapters (41)
- 0:00Introduction
- 0:34Why Microservices
- 2:22Advantages
- 4:16Infrastructure
- 5:02Logging
- 7:18Metrics
- 9:01Deployment
- 9:34Continuous Integration
- 12:20Service Template
- 12:53Sharing Code
- 13:47Multiple Environments
- 16:01Engineering Time
- 16:41Architecture
- 18:42Technology
- 19:13Testing
- 20:49HTTP
- 22:11Asynchronous Events
- 23:02Deadletter Mechanism
- 23:58Rabbit
- 24:36Kafka
- 26:04Locality of Reference
- 30:21Microservices Architecture
- 33:23CQRS
- 36:05Reactive
- 36:22Create new services
- 37:35Dont create services
- 38:34Conways
- 39:45Feature Changes
- 40:22Cross Boundaries
- 40:44Code Reviews
- 41:31Release Process
- 42:12Continuous Delivery
- 42:26Monitoring
- 43:01Troubleshooting
- 43:26increment
- 44:00high freedom high responsibility
- 44:34deployment pipeline
- 45:09miscellaneous advice
- 45:25service names
- 46:53new feature
- 48:59summary
