Microservices: 5 things I wish I'd known
summary
Atlassian exposes concrete practices: Confluence runs ~8,000 build jobs a week and 33,000 automated tests, so teams shrink and isolate services to restore velocity; deploy artifacts as Docker with declarative YAML that generates CloudFormation (moving toward Kubernetes), log to Splunk/Datadog, add circuit breakers/Hystrix, trace with Jaeger, and mock dependencies with WireMock while exploring Pact for contract tests. Service-to-service auth uses ASAP JWT tokens (Java, Python, Node, Go libraries). Teams own, build and run each service 24/7.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 7:11Basics of microservices
- 12:54Microservice deployments
- 17:49Testing in microservices
- 23:06Security for microservices
- 26:37Operations and failure handling
- 33:11Decomposing monoliths
- 37:52Key takeaways and Q&A
related talks
40mMicroservices: 5 things I wish I'd known
45mMicroservices: A retrospective
52mMicroservices: A Utopian Mystery
25mMaking microservices a behaviour not a buzzword
23mMicroservices – Sean Smith
36mWild Microservices and Imaginary DevOps
57mHow Do I Secure My Micro-Services?
01h 03mThe Magic of Small Things - 10 Years of Microservices