Hiding The Lead: Coupling, Cohesion, and Microservices-Style
summary
Argues that microservices only deliver independent deployability if interfaces are stable and internal details are hidden, citing David Parnas (1971) and showing four coupling types: domain coupling, pass‑through coupling, common coupling, and content coupling (the last causing distributed monoliths). Recommends explicit schemas and build‑time checks using tools like proto-lock and OpenAPI diff, preferring DTOs or annotated mappings over automatic serialization, and insists: never reach into another service’s database — hide as much information as possible.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 1:51Why microservices need hiding
- 6:43Modular software and information hiding
- 9:31Microservices as modular architecture
- 11:15Hiding secrets in microservices
- 17:14Explicit contracts and schemas
- 21:02Coupling and cohesion explained
- 25:12Types of coupling in microservices
- 30:47Common and content coupling
- 37:45Avoiding distributed monoliths
- 39:12Summary and key takeaways
- 42:40Q&A session begins
