The world is a constantly evolving place with new trends, new waves and new contexts emerging routinely; staying at the top of it all is what businesses try to do.
It is with this sad note, we must look back at our MVC model of developing web apps and say “Good bye, old friend.”
MVC was good to us in the traditional era of pure synchronous web apps where the entire app would process and render on the server-side, with a thin front-end-view-layer being delivered to the client side.
Today, as we start moving to SPAs; server-side frameworks that we build and adopt should truly be built for the SPA era. Since most web apps now rely on the servers-side code to serve API nodes; we should look to frameworks that have left the MVC model.
Slim is a good framework example of this; though not as light weight as it could be; it has adopted a middleware approach to server-side programming. The term middleware-approach is my own coinage ofcourse.
Tech teams endeavouring on new projects should keep this in mind when selecting a framework or choosing to develop their own. Unnecessary or incorrect models of development can create bad code.
