DBMS > AgensGraph vs. Apache Druid vs. GridGain vs. IBM Db2 warehouse vs. RocksDB

System Properties Comparison AgensGraph vs. Apache Druid vs. GridGain vs. IBM Db2 warehouse vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

GridGain is an in-memory computing platform, built on Apache Ignite

Cloud-based data warehousing service

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

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS
Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

Key-value store

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

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

Website

bitnine.net/agensgraph

druid.apache.org

www.gridgain.com

www.ibm.com/products/db2/warehouse

rocksdb.org

Technical documentation

bitnine.net/documentation

druid.apache.org/docs/latest/design

www.gridgain.com/docs/index.html

github.com/facebook/rocksdb/wiki

Developer

Bitnine Global Inc.

Apache Software Foundation and contributors

GridGain Systems, Inc.

IBM

Facebook, Inc.

Initial release

2016

2012

2007

2014

2013

Current release

2.1, December 2018

29.0.1, April 2024

GridGain 8.5.1

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache license v2

commercial

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

Java

Java, C++, .Net

C++

Server operating systems

Linux
OS X
Windows

Linux
OS X
Unix

Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

depending on used data model

yes

schema-less columns are supported

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.

yes

Import/export of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

SQL for querying

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

Cypher Query Language
JDBC

JDBC
RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

.NET Client API
JDBC
ODBC
OLE DB

C++ API
Java API

Supported programming languages

C
Java
JavaScript
Python

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

yes (compute grid and cache interceptors can be used instead)

PL/SQL, SQL PL

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

manual/auto, time-based

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, via HDFS, S3 or other storage engines

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

fine grained access rights according to SQL-standard

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Security Hooks for custom implementations

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.