DBMS > EJDB vs. H2 vs. TerminusDB vs. Vitess

System Properties Comparison EJDB vs. H2 vs. TerminusDB vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Spatial DBMS

Document store
RDF store

Document store
Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

github.com/Softmotions/ejdb

www.h2database.com

terminusdb.com

vitess.io

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

www.h2database.com/html/main.html

terminusdb.github.io/terminusdb/#

vitess.io/docs

Developer

Softmotions

Thomas Mueller

DataChemist Ltd.

The Linux Foundation, PlanetScale

Initial release

2012

2005

2018

2013

Current release

2.2.220, July 2023

11.0.0, January 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GPLv2

Open Source

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

Open Source

GPL V3

Open Source

Apache Version 2.0, commercial licenses available

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

Prolog, Rust

Server operating systems

server-less

All OS with a Java VM

Linux

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (WOQL)

yes

with proprietary extensions

APIs and other access methods

in-process shared library

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Java

JavaScript
Python

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

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

Journaling Streams

Multi-source replication
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 across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

in-memory journaling

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

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

[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

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

provided by Google 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

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

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