Building Systems that are #neverdone
summary
Argues microservices let a system last while individual components are replaced, but they break end-to-end testing and force new practices: prefer lots of unit tests and TDD, avoid shared domain libraries (allow copy and paste and use a service template like Spring Boot/Dropwizard for infra), run consumer-driven contracts (Pact) in CI, and do semantic monitoring and testing in production with canary or blue‑green deploys; claims these approaches reduce blast radius and work in practice at companies like Netflix.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:40What is neverdone
- 5:30Microservices
- 8:23Singularity
- 12:56Problems
- 16:54Integration
- 19:57Other practices
- 24:29The Agony
- 26:56Grasp
- 35:39Testdriven development
- 38:37Should we bother with TDD
- 42:16SRP
- 44:09KISS
- 45:41Application Servers
- 48:44Integration Testing
related talks
40mKill "Microservices" before its too late
36mIt's Simple...
50mEmbracing Microservices
45mBuilding a successful test automation architecture in a microservices environment
46mLove Your Monolith
57mEmbracing Microservices
54mServices, Services, Everywhere!
50mTactics and strategies on software development: how to reach ...