Hiding The Lead

on YouTube ↗46m

" summary

Argues that microservice success depends on independent deployability and that old structured‑programming ideas — information hiding, cohesion and several distinct kinds of coupling — still decide whether services can evolve. Calls out three coupling types: domain coupling (normal service-to-service contracts), common coupling (shared data stores), and content coupling (pathological direct DB access, seen surprisingly often). Recommends explicit contracts: DTOs, JSON Schema or Avro, protocol buffers with tooling like protolock, plus tests and APIs instead of reaching into another service’s implementation.

AI-written summary · about

" chapters (13)

1. 0:00Introduction
2. 1:35Independent Deployability
3. 4:43Modules
4. 8:41Information Hiding
5. 10:47Explicit
6. 14:43Data Transfer Object
7. 16:05Module Connections
8. 18:02Schemas
9. 22:58Cohesion
10. 26:55Domain Coupling
11. 30:06Common Coupling
12. 37:25Summary
13. 40:05QA

" related talks

• 51mHiding The Lead: Coupling, Cohesion, and Microservices-StyleSam Newman · Build Stuff 2020
• 44mHiding The LeadSam Newman · Craft Conference 2021
• 53mHiding The LeadSam Newman · NDC London 2021
• 37mHiding The LeadSam Newman · Build Stuff 2021
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 48mI Made Everything Loosely Coupled. Does My App Fall Apart?Gregor Hohpe · GOTO EDA Day 2022
• 48mBalancing Coupling in Software DesignVladik Khononov · Craft Conference 2022
• 56mDesigning in the World of MicroservicesVenkat Subramaniam · Developers Summit 2021