Summary
We went through a real whirlwind of different database technologies. While we looked at the same seven functions over and over, it's useful to be exposed to the various data storage models and ways of getting things done. Even so, we only touched the surface of options for accessing databases and data storage engines from Node.js.
By abstracting the model implementations correctly, we were able to easily switch data storage engines while not changing the rest of the application.
By focusing the model code on the purpose of storing data, both the models and the application should be easier to test. The application can be tested with a mock data module that provides known predictable notes that can be checked predictably. We'll look at this in more depth in Chapter 11, Unit Testing.
In the next chapter, we'll focus on deploying our application for real use by real people.
