DBMS > Dgraph vs. EsgynDB vs. Google Cloud Bigtable vs. RocksDB vs. Sphinx

System Properties Comparison Dgraph vs. EsgynDB vs. Google Cloud Bigtable vs. RocksDB vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Graph DBMS

Relational DBMS

Key-value store
Wide column store

Key-value store

Search engine

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

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

dgraph.io

www.esgyn.cn

cloud.google.com/bigtable

rocksdb.org

sphinxsearch.com

Technical documentation

dgraph.io/docs

cloud.google.com/bigtable/docs

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Dgraph Labs, Inc.

Esgyn

Google

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2016

2015

2013

2001

Current release

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

Open Source

GPL version 2, commercial licence available

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

C++

Server operating systems

Linux
OS X
Windows

Linux

hosted

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

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

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

C++ API
Java API

Proprietary protocol

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Java Stored Procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication between multi datacenters

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

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

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.