DBMS > ArcadeDB vs. Drizzle vs. H2GIS vs. OrigoDB vs. Riak TS

System Properties Comparison ArcadeDB vs. Drizzle vs. H2GIS vs. OrigoDB vs. Riak TS

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

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

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

Spatial extension of H2

A fully ACID in-memory object graph database

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Spatial DBMS

Document store
Object oriented DBMS

Time Series DBMS

Secondary database models

Relational 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	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

arcadedb.com

www.h2gis.org

origodb.com

Technical documentation

docs.arcadedb.com

www.h2gis.org/docs/home

origodb.com/docs

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Arcade Data

Drizzle project, originally started by Brian Aker

CNRS

Robert Friberg et al

Open Source, formerly Basho Technologies

Initial release

2021

2008

2013

2009

under the name LiveDB

2015

Current release

September 2021

7.2.4, September 2012

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

Open Source

LGPL 3.0

Open Source

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Java

Erlang

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X

Linux
Windows

Linux
OS X

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-like query language, no joins

yes

with proprietary extensions

yes

yes, limited

APIs and other access methods

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

JDBC

.NET Client API
HTTP API
LINQ

HTTP API
Native Erlang Interface

Supported programming languages

Java

C
C++
Java
PHP

Java

.Net

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

based on H2

yes

Erlang

Triggers

hooks for callbacks inside the server can be used.

yes

Domain Events

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

based on H2

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

depending on model

links between datasets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

based on H2

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page