DBMS > AlaSQL vs. LevelDB vs. OushuDB vs. PouchDB vs. Snowflake

System Properties Comparison AlaSQL vs. LevelDB vs. OushuDB vs. PouchDB vs. Snowflake

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

A data warehouse powered by Apache HAWQ supporting descriptive analysis and advanced machine learning

JavaScript DBMS with an API inspired by CouchDB

Cloud-based data warehousing service for structured and semi-structured data

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	0.10
Rank	#355	Overall
	#154	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

alasql.org

github.com/google/leveldb

www.oushu.com/product/oushuDB

pouchdb.com

www.snowflake.com

Technical documentation

github.com/AlaSQL/alasql

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

www.oushu.com/documentation

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

Developer

Andrey Gershun & Mathias R. Wulff

Google

Oushu

Apache Software Foundation

Snowflake Computing Inc.

Initial release

2014

2011

2012

2014

Current release

1.23, February 2021

4.0.1, August 2020

7.1.1, June 2019

License

Commercial or Open Source

Open Source

MIT-License

Open Source

BSD

commercial

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

JavaScript

C++

JavaScript

Server operating systems

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

Illumos
Linux
OS X
Windows

Linux

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

hosted

Data scheme

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

via views

SQL

Support of SQL

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

Full-featured ANSI SQL support

yes

APIs and other access methods

JavaScript API

JDBC
ODBC

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

JavaScript

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C
C++

JavaScript

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

with a proxy-based framework, named couchdb-lounge

yes

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

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

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

ACID

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

Kerberos, SSL and role based access

Users with fine-grained authorization concept, user roles and pluggable authentication

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.