Reading the article, I'm not sure if that's an alternative so much as a prerequisite. Looking at the monolithic architecture, it just took each feature within

Reading the article, I'm not sure if that's an alternative so much as a prerequisite. Looking at the monolithic architecture, it just took each feature within the monolith and created it as a microservice. Just because you have a monolith doesn't mean you can't have well thought out features and separations of concern. Before coding, before deciding on architecture, I like to think in these terms. What features make the most sense together? Far apart? It should be a prerequisite of any project, regardless of architecture. If you're building a monolith, each one just goes in a different module or package rather than having its own service.