Hiding The Lead
summary
Argues that information hiding is the essential practice to achieve independent deployability, advocating minimal APIs, explicit schemas and CI checks (JSON Schema, OpenAPI diff, schema registry, protobuf examples) to catch structural breaks. Classifies coupling into domain coupling, common coupling and content coupling, showing content coupling (direct DB access) causes duplicated logic and fragile systems. Recommends sagas over distributed transactions, prefers starting with a monolith then evolving, and using managed cloud services to avoid premature operational complexity.
AI-written summary · about
chapters (18)
- 0:00Start
- 0:06Sam Newman
- 0:53Microservices
- 2:02Independent Deployability
- 6:46Software Architecture
- 7:42Hot Swapping of Modules
- 9:49Information Hiding
- 10:43Accounts Microservice
- 16:29Explicit Contract
- 19:06Coupling and Cohesion
- 21:18Layered Architectures
- 22:47Domain Coupling
- 24:27Common Coupling
- 26:07Content Coupling
- 28:47Low Cohesion
- 29:48Pathological Coupling
- 30:59Questions
- 34:43Semantic Breakages
