Surviving in a Microservices Environment
summary
Checklist of concrete outcomes and tools: centralized logging is nonnegotiable—ELK self‑hosted fills disks so the team switches to Loggly and keeps logs searchable; metrics feed Grafana and Datadog style alerts; CI uses Jenkinsfile pipelines to spawn ephemeral Docker test environments that build branch images and upload failures to S3; Kubernetes and minikube power per‑developer namespaces; avoid shared business logic, keep services fewer than developers, expect SREs to become essential.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:51Microservices
- 1:26Advantages and Challenges
- 4:17Infrastructure
- 4:57Log Management
- 7:15Metrics
- 9:58Scaling
- 13:05Builds
- 14:33Deployment
- 15:10Coding conventions
- 16:37Service templates
- 17:02How to share code
- 18:02Managing multiple environments
- 19:40Testing and isolation
- 21:38Design vision
- 21:57Choosing technologies
- 22:23Testing
- 22:44Testing the Platform
- 23:04Monitor Error Rates
- 23:23HTTP vs Async
- 24:13Domain Driven Design
- 25:40Team Communication
- 26:30Naming Services
