Interview with James Lewis
summary
Microservices are presented as a 40 year old set of complementary practices that coalesce into a pattern language rather than a marketing platform. Key claims: prefer choreography over orchestration, give services ownership of their own data, and rely on continuous delivery to push changes independently. Infrastructure tools cited include Chef Puppet Ansible plus Netflix OSS components like Hystrix Dropwizard and Chaos Monkey. Large adopters run hundreds of services — Netflix 650+ services and 40+ open source projects — and use event buses and event sourcing for cross‑service communication.
AI-written summary · about
chapters (8)
- 0:00Microservices introduction
- 1:08Origins and practices
- 3:37Core patterns
- 6:47Deployment and consistency
- 8:53Monolith vs microservices
- 11:41Reactive apps and event sourcing
- 13:48Infrastructure for microservices
- 15:31Operational maturity
related talks
02mThe O’Reilly Software Architecture Conference - New York, NY
15mFireside Chat with AWS and Redmonk | AWS Developer Day 2025
26mFireside Chat with Jeff Barr of AWS
04mBrent Beer - Keynoter at Codemotion Milan 2017 - Interview
26mCollaborate Like You Mean it: The End of Siloed API Development
34mInterview with
11mKeynote: Stitching Things Together
32mTransformed! A Musical DevOps Journey