Local First Database Comparison

In this project I have implemented the exact same chat application with different local first database technologies. You can use it to compare metrics and learn about the differences. The chat app is a web based angular application, with functionality similar to Whatsapp Web.

Implemented Databases:

• AWS Amplify Datastore
• Firebase Firestore
• PouchDB with IndexedDB adapter & CouchDB replication
• RxDB LokiJS with LokiJS Storage & GraphQL replication
• RxDB Dexie.js with Dexie.js Storage & GraphQL replication
• WatermelonDB with LokiJS adapter (no backend sync atm)

Metrics

All metrics are measured automatically via code in a browser tests (chrome:headless). The results heavily depend on the developers device. You should compare the values relative to another and not as absolute values. Also you might want to create new metrics that better represent how you would use the respective database.

You can reproduce these values by running sh measure-metrics.sh in the root folder.

Metric \ Project	aws	firebase	pouchdb	rxdb-dexie	rxdb-lokijs	watermelondb
First angular component render	231ms	259ms	219ms	188ms	207ms	202ms
Page load time	289ms	207ms	275ms	250ms	267ms	259ms
First full render	390ms	746ms	826ms	473ms	595ms	275ms
Insert one message	16ms	262ms	16ms	18ms	8ms	5ms
Inserting 20 messages one after another	433ms	4639ms	241ms	223ms	167ms	107ms
Inserting 20 messages in parallel	105ms	3749ms	88ms	226ms	37ms	104ms
Message insert to message list change	39ms	17ms	129ms	18ms	7ms	4ms
Message search query time	362ms	210ms	186ms	37ms	22ms	23ms
First full render with many messages	438ms	852ms	1288ms	636ms	606ms	304ms
Storage usage	239kb	427kb	1971kb	1089kb	2742kb	2164kb
Bundle size, plain JavaScript	1833kb	952kb	791kb	1075kb	1067kb	955kb
Bundle size, minified+gzip	421kb	235kb	190kb	266kb	254kb	217kb

Metrics Explanation

• Page load time: How long does it take to download and parse the JavaScript bundle.
• First angular component render: How long does it take for the first angular component to be rendered.
• First full render: How long does it take until all relevant data is displayed for the first time.
• Insert one message: How long does it take to insert a single message.
• Inserting 20 messages one after another: How long does it take to insert 20 messages in serial.
• Inserting 20 messages in parallel: How long does it take to insert 20 messages in parallel.
• Message insert to message list change: How long does it take until a new message is rendered to the dom.
• User change to message list change: How long does it take from changing the user to the displaying of the new messages list.
• Message search query time: How long does it take to search for a given message by regex/like-operator.
• First full render with many messages: Time to first full render when many messages exist.
• Storage usage: Size of the stored IndexedDB database after inserting the full test dataset.
• Bundle size, plain JavaScript: The full JavaScript bundle size, without minification or gzip.
• Bundle size, minified+gzip: The full JavaScript bundle size after minification and gzip compression.

Investigations

Why is LokiJS so much faster?

WatermelonDB and the RxDB-LokiJS project use the LokiJS database as storage, which is an in memory database that regularly persists the data to IndexedDB either on interval, or when the browser tab is closed. By doing so, less slow IndexedDB transaction are used. Keeping and processing the data in memory has the benefit of being much faster, but it also has its downsides:

• Initial page load is much slower when much data is already stored in the database, because all data must be loaded before any database operation can be done.
• All data must fit into memory.
• Data can be lost when the JavaScript process is killed ungracefully like when the browser crashes or the power of the PC is terminated.
• There is no multi-tab-support with plain LokiJS. The data is not shared between multiple browser tabs of the same origin. RxDB handles that by adding its own multi tab handling via the BroadcastChannel module.

Why is Firebase so slow on first render?

On the first page load, Firebase ensures that the local data is equal to the server side state. This means that the client has to be online at application startup which is the reason why Firebase is not completely offline first. To ensure the equalness of client side data, Firebase has to perform several requests to the backend, before the database will respond to queries. This makes the inital page load slow, and it becomes even more slower, the more data exists and has to be validated.

Why is PouchDB so slow?

For the PouchDB and RxDB (with PouchDB storage) I used the old Indexeddb adapter. It is much less optimized than the new adapter, but the new one made problems with returning the correct query results. Theses problems have been fixed on the PouchDB master branch, but I have to wait for the next PouchDB release. I will update the repo when this change can be done.

Why does AWS Datastore need so much less storage space?

AWS Datastore does not save any metadata together with the documents. Instead only the plain documents are stored in IndexedDB. They can do this because they only allow simple queries and do not keep a local version history.

Feature Map

Feature \ Project	aws	firebase	pouchdb	rxdb-lokijs	rxdb-dexie	watermelondb
Offline First	No, login required	Partially, must be online on first page load	Yes	Yes	Yes	Yes
Realtime Replication	Yes	Yes	Yes	Yes	Yes	Partially, must be implemented by hand
Multi Tab Support	Yes	Yes	No	Yes	Yes	Partially, relies on online sync
Observable Queries	No	Yes	No	Yes	Yes	Yes
Complex Queries	No	Yes	Yes	Yes	Yes	Yes
Client Side Encryption	No	No	Yes	Yes	Yes	No
Schema Support	Yes	No	No	Yes	Yes	Yes
Custom Backend	No	No	No	Yes	Yes	Yes
Custom Conflict Handling	Yes	No	Yes	Yes	Yes	No

Starting the projects

All sub-projects use the same port and so can not be started in parallel.

Installation

• You must have installed Node.js
• Clone this project
• In the root folder, run npm install to install the dependencies.
• In the root folder, run npm run build to build all projects.

Firebase Firestore

• Run npm run start:firebase to start the mock server and the production build frontend.

• Or run npm run dev:firebase to start the mock server and the development frontend server.

• Open http://localhost:3000/ to browse the frontend.

AWS Amplify & Datastore

The official AWS mock does not allow a live replication at this point. So you first have to setup an amplify project in the ./projects/aws folder by using this tutorial

• Run npm run start:aws to start the mock server and the production build frontend.

• Or run npm run dev:aws to start the mock server and the development frontend server.

• Open http://localhost:3000/ to browse the frontend.

PouchDB

• Run npm run start:pouchdb to start the mock server and the production build frontend.

• Or run npm run dev:pouchdb to start the mock server and the development frontend server.

• Open http://localhost:3000/ to browse the frontend.

RxDB LokiJS

• Run npm run start:rxdb-lokijs to start the mock server and the production build frontend.

• Or run npm run dev:rxdb-lokijs to start the mock server and the development frontend server.

• Open http://localhost:3000/ to browse the frontend.

RxDB Dexie.js

• Run npm run start:rxdb-dexie to start the mock server and the production build frontend.

• Or run npm run dev:rxdb-dexie to start the mock server and the development frontend server.

• Open http://localhost:3000/ to browse the frontend.

WatermelonDB

• Run npm run start:watermelondb to start the mock server and the production build frontend.

• Or run npm run dev:watermelondb to start the mock server and the development frontend server.

• Open http://localhost:3000/ to browse the frontend.

TODOs

Pull requests are welcomed. Please help implementing more examples:

• Meteor (with the IndexedDB offline first plugin).
• WatermelonDB backend replication.
• AWS Ampflify local backend mock with realtime replication.
• GunDB.