DBMS > Drizzle vs. RavenDB vs. Snowflake vs. SQL.JS vs. TerminusDB

System Properties Comparison Drizzle vs. RavenDB vs. Snowflake vs. SQL.JS vs. TerminusDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Port of SQLite to JavaScript

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

Technical documentation

ravendb.net/docs

docs.snowflake.net/manuals/index.html

sql.js.org/documentation/index.html

terminusdb.github.io/terminusdb/#

Developer

Drizzle project, originally started by Brian Aker

Hibernating Rhinos

Snowflake Computing Inc.

Alon Zakai

enhancements implemented by others

DataChemist Ltd.

Initial release

2008

2010

2014

2012

2018

Current release

7.2.4, September 2012

5.4, July 2022

11.0.0, January 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

AGPL version 3, commercial license available

commercial

Open Source

GPL V3

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

C++

JavaScript

Prolog, Rust

Server operating systems

FreeBSD
Linux
OS X

Linux
macOS
Raspberry Pi
Windows

hosted

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

Linux

Data scheme

yes

schema-free

yes

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

yes

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

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

JDBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

CLI Client
JDBC
ODBC

JavaScript API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
C++
Java
PHP

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

JavaScript

JavaScript
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

hooks for callbacks inside the server can be used.

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

yes

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

except by serializing a db to a file

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Authorization levels configured per client per database

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

Role-based access control

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.