DBMS > Apache Kylin vs. Dgraph vs. EsgynDB vs. GigaSpaces vs. RocksDB

System Properties Comparison Apache Kylin vs. Dgraph vs. EsgynDB vs. GigaSpaces vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

Distributed and scalable native Graph DBMS

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

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

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Key-value store

Secondary database models

Graph DBMS
Search engine

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

Score	1.25
Rank	#170	Overall
	#77	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

Technical documentation

kylin.apache.org/docs

dgraph.io/docs

docs.gigaspaces.com/latest/landing.html

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation, originally contributed from eBay Inc

Dgraph Labs, Inc.

Esgyn

Gigaspaces Technologies

Facebook, Inc.

Initial release

2015

2016

2015

2000

2013

Current release

3.1.0, July 2020

15.5, September 2020

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2; Commercial licenses available

Open Source

BSD

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

Java

C++, Java

Java, C++, .Net

C++

Server operating systems

Linux

Linux
OS X
Windows

Linux

Linux
macOS
Solaris
Windows

Linux

Data scheme

yes

schema-free

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

yes

SQL-99 for query and DML statements

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

ADO.NET
JDBC
ODBC

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

C++ API
Java API

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

.Net
C++
Java
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes, event driven architecture

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication between multi datacenters

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

Planned for future releases

fine grained access rights according to SQL-standard

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.