As you learned in Chapter 1, Setup and Installation, Meteor operates on a reactive programming model. This means that your client/browser isn't only concerned with displaying data, but it's also listening for changes to that data, so that it can "react" to those changes. These areas of data, where your browser looks for changes, are called reactive contexts.
We will start our Lending Library application in earnest, laying the framework for future chapters, and using Meteor's built-in reactive contexts to track and propagate changes to our application to all clients who are listening.
In this chapter, you will learn about: