It's widely accepted that, in most cases at least, software systems should be modular, consisting of separate, discrete services. But what about the size of those services? How big or small should they be? This is where the question of service granularity comes in: too small and your system will become needlessly complicated; too big and you lose all the benefits of modularity you were seeking in the first place.

In this episode of the Thoughtworks Technology Podcast, host Ken Mugrage is joined by Neal Ford and Mark Richards — authors of multiple books on software architecture — to discuss service granularity. They explain why it matters and how software architects can go about getting it right, through the lens of granularity integrators and disintegrators.

 

Learn more about Neal and Mark's 2021 book Software Architecture: The Hard Parts (co-authored with Zhamak Dehghaniand Pramod Sadalage): https://www.thoughtworks.com/insights/books/software-architecture-hard-parts

Find out more about Neal and Mark's second edition of The Fundamentals of Software Architecture, set to be released in early 2025: https://www.oreilly.com/library/view/fundamentals-of-software/9781098175504/