No, unless you plan to have one team focused on the front-end and another on the API. In that case, it might make sense to make your code more modular (and expl

No, unless you plan to have one team focused on the front-end and another on the API. In that case, it might make sense to make your code more modular (and explains how Conway's Law [0] comes about) Otherwise, it's easier to support one monolith. Imagine having to change some back-end code that your front-end code relies on. This could be accomplished in one deployment with a monolith, but would require two deployments if you separate the FE and API. Not only that, but it would require you to keep them in sync or version your API. [0] https://en.wikipedia.org/wiki/Conway%27s_law https://en.wikipedia.org/wiki/Conway%27s_law