DBMS > H2 vs. RavenDB vs. Snowflake vs. Transbase vs. Yanza

System Properties Comparison H2 vs. RavenDB vs. Snowflake vs. Transbase vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

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

A resource-optimized, high-performance, universally applicable RDBMS

Time Series DBMS for IoT Applications

Primary database model

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	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

www.h2database.com

ravendb.net

www.snowflake.com

www.transaction.de/en/products/transbase.html

yanza.com

Technical documentation

www.h2database.com/html/main.html

ravendb.net/docs

docs.snowflake.net/manuals/index.html

www.transaction.de/en/products/transbase/features.html

Developer

Thomas Mueller

Hibernating Rhinos

Snowflake Computing Inc.

Transaction Software GmbH

Yanza

Initial release

2005

2010

2014

1987

2015

Current release

2.2.220, July 2023

5.4, July 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

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

Open Source

AGPL version 3, commercial license available

commercial

free development license

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C and C++

Server operating systems

All OS with a Java VM

Linux
macOS
Raspberry Pi
Windows

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Windows

Data scheme

yes

schema-free

yes

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

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (RQL)

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

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

Java

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

JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

none

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

yes

Source-replica replication

none

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.

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

ACID

yes

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

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

fine grained access rights according to SQL-standard

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.