There is no "one-size-fits-all" architecture and the choice should be made based on not only the project itself, but the team as well. One-and-a-half developer team will be perfectly fine with a monolith, modular or not. A cross-functional team of a dozen specialists will thrive with micro-services. And yes, there is a middle-ground where some parts of the deployment are "micro" and the others are not.
I agree, "it depends" is a trully valid answer when choosing the architecture for your project. I wrote about the same when choosing micro-frontends and my friend @lucamezzalira
has a really nice article about the decisions framework.
There is no "one-size-fits-all" architecture and the choice should be made based on not only the project itself, but the team as well. One-and-a-half developer team will be perfectly fine with a monolith, modular or not. A cross-functional team of a dozen specialists will thrive with micro-services. And yes, there is a middle-ground where some parts of the deployment are "micro" and the others are not.
I agree, "it depends" is a trully valid answer when choosing the architecture for your project. I wrote about the same when choosing micro-frontends and my friend @lucamezzalira has a really nice article about the decisions framework.
medium.com/@lucamezzalira/micro-fr...