I am going to compare to Ruby on Rails because of its structure and popularity. Here we have a classic example
The first part here is the server, represented by a UI (on the server) where a user interacts. The server.coffee file
It's a holistic design and it really simplifies data exchange services in an abstract way. The route determines which path to take and removes a step in MVC. The route now includes all code to process the
Some may argue that this is breaking MVC and it is, but here's why it's advantageous. Rails controllers get bloated quickly, and everyone has their own idea of what code should go where in the model vs the controller. Here we ignore that, simply use our route to exclusively save user input and chain us to the next step. Any manipulation to the data is done in the background giving a big performance gain and enables greater horizontal scaling.