DBMS > ArcadeDB vs. Dgraph vs. H2 vs. Postgres-XL vs. Snowflake

System Properties Comparison ArcadeDB vs. Dgraph vs. H2 vs. Postgres-XL vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

Distributed and scalable native Graph DBMS

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Graph DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.02
Rank	#366	Overall
	#50	Document stores
	#38	Graph DBMS
	#53	Key-value stores
	#36	Time Series DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

docs.arcadedb.com

dgraph.io/docs

www.h2database.com/html/main.html

www.postgres-xl.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Arcade Data

Dgraph Labs, Inc.

Thomas Mueller

Snowflake Computing Inc.

Initial release

2021

2016

2005

2014

since 2012, originally named StormDB

2014

Current release

September 2021

2.2.220, July 2023

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

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

Open Source

Mozilla public license

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

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

All OS with a Java VM

Linux
macOS

hosted

Data scheme

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

XML type, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

distributed, parallel query execution

yes

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

CLI Client
JDBC
ODBC

Supported programming languages

Java

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

Java

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

none

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication via Raft

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Planned for future releases

fine grained access rights according to SQL-standard

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.