One of the things that I liked when React landed on the scene in the Javascript world is that it led us to think about composition and modularity in a more rigo

One of the things that I liked when React landed on the scene in the Javascript world is that it led us to think about composition and modularity in a more rigorous way. It didn't force us to change how we organized our file systems or repositories, but it did force us to think about how we built our components in a way that ultimately prevented problems that we often see in large codebases. What I often see missing in the monolith-vs-microservice debate is that breaking a poorly designed monolith into microservices will lead to poorly designed microservices, but if you invest in improving the modularity of your monolith, there's a lot of potential to improve the pain without needing to migrate to microservices. That said, I am not a microservices detractor. In fact, for new projects, I like to start out by asking whether microservices would be our best option. However, having been involved in some monolith-to-microservice transitions, I have seen that if you don't approach it with the right mindset, you're going to spend a lot of engineering time and be no better off.