DBMS > H2 vs. RavenDB vs. Sequoiadb vs. Snowflake

System Properties Comparison H2 vs. RavenDB vs. Sequoiadb vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Open Source Operational and Transactional Enterprise NoSQL Document Database

NewSQL database with distributed OLTP and SQL

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

Primary database model

Relational DBMS

Document store

Document store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	8.22
Rank	#50	Overall
	#32	Relational DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.48
Rank	#260	Overall
	#41	Document stores
	#121	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

www.h2database.com/html/main.html

ravendb.net/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.snowflake.net/manuals/index.html

Developer

Thomas Mueller

Hibernating Rhinos

Sequoiadb Ltd.

Snowflake Computing Inc.

Initial release

2005

2010

2013

2014

Current release

2.2.220, July 2023

5.4, July 2022

License

Commercial or Open Source

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

AGPL version 3, commercial license available

Open Source

Server: AGPL; Client: Apache V2

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

Java

C++

Server operating systems

All OS with a Java VM

Linux
macOS
Raspberry Pi
Windows

Linux

hosted

Data scheme

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL-like query language (RQL)

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

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

proprietary protocol using JSON

CLI Client
JDBC
ODBC

Supported programming languages

Java

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

.Net
C++
Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

With clustering: 2 database servers on different computers operate on identical copies of a database

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Document is locked during a transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

simple password-based access control

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.