DBMS > DataFS vs. EsgynDB vs. Riak KV vs. Warp 10

System Properties Comparison DataFS vs. EsgynDB vs. Riak KV vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Distributed, fault tolerant key-value store

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Object oriented DBMS

Relational DBMS

Key-value store

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

Time Series DBMS

Secondary database models

Graph DBMS

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

newdatabase.com

www.esgyn.cn

www.warp10.io

Technical documentation

dev.mobiland.com/Overview.xsp

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

www.warp10.io/content/02_Getting_started

Developer

Mobiland AG

Esgyn

OpenSource, formerly Basho Technologies

SenX

Initial release

2018

2015

2009

2015

Current release

1.1.263, October 2022

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

Apache License 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

Server operating systems

Windows

Linux

Linux
OS X

Linux
OS X
Windows

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
C
C#
C++
VB.Net

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

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

yes

WarpScript

Triggers

no, except callback-events from server when changes happened

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

Sharding

no "single point of failure"

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

selectable replication factor

based on HBase

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

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

links between data sets can be stored

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.

yes

User concepts

Access control

Windows-Profile

fine grained access rights according to SQL-standard

yes, using Riak Security

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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

Time Series Databases Software Market [2024-2031] | InfluxData, Trendalyze, Amazon Timestream
11 May 2024, Motions Online

Time Series Intelligence Software Market Business Insights, Key Trend Analysis | Google, SAP, Azure Time Series ...
24 April 2024, Amoré

Time Series Intelligence Software Market Analysis and Revenue Prediction | Azure Time Series Insights, Trendalyze ...
20 May 2024, Weekly Post Gazette

provided by Google News

Share this page