DBMS > OrigoDB vs. TerminusDB vs. Vitess vs. XTDB

System Properties Comparison OrigoDB vs. TerminusDB vs. Vitess vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fully ACID in-memory object graph database

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Scalable, distributed, cloud-native DBMS, extending MySQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Object oriented DBMS

Graph DBMS

Relational DBMS

Document store

Secondary database models

Document store
RDF store

Document store
Spatial DBMS

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

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

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

origodb.com

terminusdb.com

vitess.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

origodb.com/docs

terminusdb.github.io/terminusdb/#

vitess.io/docs

www.xtdb.com/docs

Developer

Robert Friberg et al

DataChemist Ltd.

The Linux Foundation, PlanetScale

Juxt Ltd.

Initial release

2009

under the name LiveDB

2018

2013

2019

Current release

11.0.0, January 2023

15.0.2, December 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

GPL V3

Open Source

Apache Version 2.0, commercial licenses available

Open Source

MIT 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

Prolog, Rust

Clojure

Server operating systems

Linux
Windows

Linux

Docker
Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

yes, extensible-data-notation format

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

SQL

Support of SQL

SQL-like query language (WOQL)

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

.NET Client API
HTTP API
LINQ

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST
JDBC

Supported programming languages

.Net

JavaScript
Python

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

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

Graph Partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Journaling Streams

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

depending on model

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

in-memory journaling

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Role based authorization

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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

How TerminusDB is commercializing its open source graph database
16 March 2021, VentureBeat

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Dublin-based data collaboration tool TerminusDB raises €3.6 million in seed round
15 March 2021, Tech.eu

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source ...
12 April 2022, United Nations Office for Disaster Risk Reduction

provided by Google News

Vitess, the database clustering system powering YouTube, graduates CNCF incubation
5 November 2019, SiliconANGLE News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Share this page