Checkpoints[05]

PouchDB allows users to enable or disable replication checkpoints (which would be modified based on system performance goals and/or usage), which are used for synchronization across the local and remote servers.

Compression[06]

PouchDB doesn't currently support compression by default, however there is a plugin (Transform Pouch) that allows for compression of data.

Data Model[07][08]

PouchDB uses an unstructured document data model, where documents are JSON serializable. It also supports attachments, which store binary data.

Foreign Keys[09]

Indexes[10]

Starting with version 2.2.0, PouchDB supports secondary indexes using B-trees. The default index is build on the _id field.

Logging

TODO: can't unselect / delete this option.

Query Execution

PouchDB can use map/reduce or create MangoQueries (used to build secondary indexes). Users can create an empty query to speed up the query. By dividing into map and reduce, parallelism can speed up the process.

Query Interface[11]

PouchDB utilizes a custom API for its query interface. As it is designed for web browsers, this API supports callbacks, promises, and async functions.

Storage Organization[12][13]

When offline, data is stored locally using WebSQL (deprecated) or IndexedDB, depending on the browser. For IndexedDB usage, the method of storage organization is ISAM. When online, data synchs with CouchDB (and other servers). CouchDB storage uses copy-on-write to update database files. (TODO: select two options).

Stored Procedures[09]

PouchDB allows for stored procedures by using view functions in JavaScript.

Views[07][14]

PouchDB supports creating materialized views of the results of a query. It's very similar to CouchDB however PouchDB uses ASCII ordering to order view query keys. It also does not support the offset property that CouchDB does. Instead, a skip parameter is used instead of an actual offset.