DBMS > AlaSQL vs. LevelDB vs. PouchDB vs. RocksDB vs. Warp 10

System Properties Comparison AlaSQL vs. LevelDB vs. PouchDB vs. RocksDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

JavaScript DBMS with an API inspired by CouchDB

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store
Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

alasql.org

github.com/google/leveldb

pouchdb.com

rocksdb.org

www.warp10.io

Technical documentation

github.com/AlaSQL/alasql

github.com/google/leveldb/blob/main/doc/index.md

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

Andrey Gershun & Mathias R. Wulff

Google

Apache Software Foundation

Facebook, Inc.

SenX

Initial release

2014

2011

2012

2013

2015

Current release

1.23, February 2021

7.1.1, June 2019

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

BSD

Open Source

BSD

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

C++

JavaScript

C++

Java

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Illumos
Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Linux
OS X
Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

via views

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

APIs and other access methods

JavaScript API

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

JavaScript

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

only for local storage and DOM-storage

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

with automatic compression on writes

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Mandatory use of cryptographic tokens, containing fine-grained authorizations

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.