The *page model* (also known as the *read/write model*) is a simple model that can be nicely motivated from looking at the way data pages are accessed (i.e., read or written) at the storage layer of a database system. As will be seen shortly, this model is simple enough to capture the essence of the concurrency control and recovery problem in a concise and elegant way, yet it is general enough to describe many ( but not all) important system implementation issues. The major limitation of the page model is that it captures no semantics of the data access operations, given the simple low-level nature of page reads and writes.
[…] In summary, the two computational models we are about to introduce differ in their definitions of data objects. For the page model, these are pages with read and write operations; for the object model, these are general objects with an encapsulated set of operations applicable to them.