DBMS > EsgynDB vs. Riak KV vs. ToroDB vs. Trafodion

System Properties Comparison EsgynDB vs. Riak KV vs. ToroDB vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Distributed, fault tolerant key-value store

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key-value store

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

Document store

Relational DBMS

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

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

www.esgyn.cn

github.com/torodb/server

trafodion.apache.org

Technical documentation

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

trafodion.apache.org/documentation.html

Developer

Esgyn

OpenSource, formerly Basho Technologies

8Kdata

Apache Software Foundation, originally developed by HP

Initial release

2015

2009

2016

2014

Current release

3.2.0, December 2022

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

AGPL-V3

Open Source

Apache 2.0

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

Java

C++, Java

Server operating systems

Linux

Linux
OS X

All OS with a Java 7 VM

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, 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

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

Java Stored Procedures

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

selectable replication factor

Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

yes, using Riak Security

Access rights for users and roles

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

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

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

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

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

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

HP Throws Trafodion Hat into OLTP Hadoop Ring
14 July 2014, Datanami

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

Low-latency, distributed database architectures are critical for emerging fog applications
7 April 2022, Embedded Computing Design

provided by Google News

Share this page