DBMS > EsgynDB vs. OrigoDB vs. Riak KV vs. TerminusDB

System Properties Comparison EsgynDB vs. OrigoDB vs. Riak KV vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A fully ACID in-memory object graph database

Distributed, fault tolerant key-value store

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

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.esgyn.cn

origodb.com

terminusdb.com

Technical documentation

origodb.com/docs

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

terminusdb.github.io/terminusdb/#

Developer

Esgyn

Robert Friberg et al

OpenSource, formerly Basho Technologies

DataChemist Ltd.

Initial release

2015

2009

under the name LiveDB

2009

2018

Current release

3.2.0, December 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPL V3

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

C++, Java

Erlang

Prolog, Rust

Server operating systems

Linux

Linux
Windows

Linux
OS X

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

restricted

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

HTTP API
Native Erlang Interface

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.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

JavaScript
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Erlang

yes

Triggers

yes

Domain Events

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

no "single point of failure"

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Source-replica replication

selectable replication factor

Journaling Streams

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

depending on model

links between data sets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

in-memory journaling

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 authorization

yes, using Riak Security

Role-based access control

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

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

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

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

Irish start-ups received €28m from Enterprise Ireland in 2021
7 April 2022, SiliconRepublic.com

Bus Terminus Update - April 26th
26 April 2021, Around DB and Life on Lantau

provided by Google News

Share this page