FDE Times: Software Architecture: The Hard Parts — weigh what you give up when you split and connect customer systems

O’Reilly’s Software Architecture: The Hard Parts (print edition 5 November 2021; ISBN 978-1-4920-8689-5) grew out of workshops by Neal Ford, Mark Richards, Pramod Sadalage and Zhamak Dehghani. It follows a fictional Sysops Squad through service granularity, contract styles, distributed transactions and splitting operational data—without claiming easy answers.

FDE Times flags two chapters as the highest-leverage reading for field work. Strict versus loose contracts: validating a customer’s full 40-field payload will break your pipeline when an unused field is renamed, while reading only the three fields you need survives change but forces you to monitor data yourself. Pulling apart operational data: reading a shared customer database is fast but couples you to an unstable internal schema; waiting for an API costs weeks but buys a stable boundary.

The review’s practical habit for FDEs is to say the cost of each option out loud—on a one-page decision note, in system-design practice, and on the CV (“chose API over direct DB reads; accepted a two-week delay for a stable boundary”)—because “integrate with customer systems” in a job ad usually means making these trade-offs every week.