Apium Hub

Last year, Apiumhub organized the Global Software Architecture Summit, a 2-day event that focused on software architecture metrics. During this event, I had the opportunity to attend the talk “Understanding the Differences Between Modularity and Granularity” by Mark Richards, an experienced, hands-on software architect and co-author of the books “Fundamentals of Software Architecture” and “Software Architecture: The Hard Parts.” In this presentation, Mark explained how modularity and granularity can be helpful to decide how an application may evolve, being split into different services or grouping them back together.

To better understand what we are talking about, let´s first understand the definition of the terms modularity and granularity (from the book Software Architecture: The Hard Parts by the same Richards, Neal Ford, Pramod Sadalage, and Zhamak Dehghani);

Modularity concerns breaking up systems into separate parts.

Granularity deals with the size of those separate parts. 

Interestingly enough, most issues and challenges within

To read the full article click on the 'post' link at the top.