While discussing the project, we talked about Object Relationship Mapper (ORM). ORMs are libraries that act as a database wrapper for the programmer. It provides you with methods to communicate with the backend and can manage multiple types of data stores. So, in case we want to switch our data store, we will have to change just one line in the configuration part of the ORM and the rest of the code will remain the same.

This also makes the code cleaner and more readable and reliable. Though it makes the application a bit slower, the trade-off is worth it.

So, now that we know how our table structure will be, we have a better and clearer idea of what our application will be like. We will be discussing how to manage our backend using an ORM in the next chapter. It will give us a better idea as to why we are using one and not talking to the data store directly.

If you notice the expectations of each module, you might guess what our routes will be like.

We will discuss...