Architecting for Change Debate
summary
Debate lays out a concrete tradeoff: starting with 10 endpoints as separate microservices means 10 codebases, 10 pipelines and 10 data stores upfront; the alternative spins a single repo in ~4 hours and grows an emergent architecture. Key tools and practices cited include Kubernetes, a simple message bus or one-day abstraction, canary deploys at ~5%, and rollbacks where a legacy service is deleted via RMR -rf after two years. Speakers quantify scale: two instances in two regions can produce 16 instances backed by eight data stores, so logging, correlation and versioning are nonnegotiable.
AI-written summary · about
chapters (5)
- 0:00Starting with microservices
- 4:23Ensuring good design
- 10:33Managing microservices
- 17:36Addressing technical debt
- 23:24Closing arguments
related talks
44mThe Art of Architecting for Scale
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
59mChoosing the Right Architecture Style Debate
01h 00mAgile Architecture
57mForking the Future: Embracing Microservices Evolution
52mI Have a Microservices Architecture and I Didn't Know.
33mFrom Enterprise Architecture to Software Design - Critical Thinking
58mThe past, present and future of Architecture