DBMS > EsgynDB vs. Google Cloud Datastore vs. Riak KV vs. RocksDB

System Properties Comparison EsgynDB vs. Google Cloud Datastore vs. Riak KV vs. RocksDB

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Distributed, fault tolerant key-value store

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Document store

Key-value store

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

Key-value store

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

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

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.esgyn.cn

cloud.google.com/datastore

rocksdb.org

Technical documentation

cloud.google.com/datastore/docs

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

github.com/facebook/rocksdb/wiki

Developer

Esgyn

Google

OpenSource, formerly Basho Technologies

Facebook, Inc.

Initial release

2015

2008

2009

2013

Current release

3.2.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Java

Erlang

C++

Server operating systems

Linux

hosted

Linux
OS X

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

using Google App Engine

Erlang

Triggers

Callbacks using the Google Apps Engine

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication using Paxos

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

links between data sets can be stored

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

yes

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes, using Riak Security

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.