Member-only story
Remake — Connect your View directly with the Model
tl; dr; — In this article, I argue that MVC/MVVC isn’t right for projects of certain size and complexity and introduce you to Remake which lets you drop the C of MVC.
This is Part 1 of a two part series on remakeand remake-serverless. Here is Part 2 which explains remake-serverless in more detail.
The Case against MVC
It is received wisdom that for web projects, the multi layer MVC/MVVC architecture is the right way to go about designing our system.
To be fair, in many cases, this architectural dogma is absolutely right. E.g., for ecommerce shops having a model (M) layer where you can add products and product related content without having to touch the website (V) is useful.
Yet, at times, following the MVC paradigm increases the complexity of a system with no discernible upside. E.g., if I am a solo developer launching an MVP, do I have to have a separate model layer?
In fact, NoSQL products like MongoDB emerged to address the need for a more flexible model whose final, stable structure you discover along the way as the product matures.
Even so, having a Model forces you to set up some sort of persistent database be it Relational or NoSQL. And this is often unnecessary for many use cases.
