DBMS > ArcadeDB vs. Dolt vs. NSDb vs. OrigoDB vs. Transbase

System Properties Comparison ArcadeDB vs. Dolt vs. NSDb vs. OrigoDB vs. Transbase

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

A MySQL compatible DBMS with Git-like versioning of data and schema

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

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

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store

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

Score	0.10
Rank	#358	Overall
	#48	Document stores
	#38	Graph DBMS
	#52	Key-value stores
	#35	Time Series DBMS

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

arcadedb.com

github.com/dolthub/dolt
www.dolthub.com

nsdb.io

origodb.com

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

Technical documentation

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

Developer

Arcade Data

DoltHub Inc

Robert Friberg et al

Transaction Software GmbH

Initial release

2021

2018

2017

2009

under the name LiveDB

1987

Current release

September 2021

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

commercial

free development license

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

Java, Scala

C and C++

Server operating systems

All OS with a Java VM

Linux
macOS
Windows

Linux
macOS

Linux
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

SQL-like query language

yes

APIs and other access methods

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

CLI Client
HTTP REST

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
Scala

.Net

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

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

depending on model

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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

Only one user is configurable, and must be specified in the config file at startup

Role based authorization

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.

Related products and services

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

More resources

Recent citations in the news

Dolt- A Version Controlled Database
29 January 2024, iProgrammer

Top Data Version Control Tools for Machine Learning Research in 2023
24 July 2023, MarkTechPost

Dolt, a Relational Database with Git-Like Cloning Features
19 August 2020, The New Stack

Data Versioning at Scale: Chaos and Chaos Management
10 February 2023, InfoQ.com

Radar Trends to Watch: July 2022 – O'Reilly
5 July 2022, O'Reilly Media

provided by Google News

Share this page