Express and the MVC paradigm

Express doesn't enforce an opinion on how you should structure the Model, View and Controller modules of your application. As we learned in the previous chapter, the blank application created by the Express Generator provides two aspects of the MVC model:

• The views directory contains template files, controlling the display portion, corresponding to the View.

• The routes directory contains code implementing the URLs recognized by the application and coordinating the response to each URL. This corresponds to the Controller.

This leaves one wondering where to put code corresponding to the Model. The role of the Model is to hold application data, changing it as instructed by the Controller, and supplying data requested by View code. At a minimum, the Model code should be in separate modules from the Controller code. This is to ensure a clean separation of concerns, for example, to ease unit testing of each.

The approach we'll use is to create a models directory as a sibling...