DBMS > Drizzle vs. GridGain vs. RocksDB vs. Teradata Aster

System Properties Comparison Drizzle vs. GridGain vs. RocksDB vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

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

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store

Relational DBMS

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

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

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

Website

www.gridgain.com

rocksdb.org

Technical documentation

www.gridgain.com/docs/index.html

github.com/facebook/rocksdb/wiki

Developer

Drizzle project, originally started by Brian Aker

GridGain Systems, Inc.

Facebook, Inc.

Teradata

Initial release

2008

2007

2013

2005

Current release

7.2.4, September 2012

GridGain 8.5.1

9.2.1, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

BSD

commercial

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, C++, .Net

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

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

yes

APIs and other access methods

JDBC

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

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C
C++
Java
PHP

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

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

R packages

Triggers

hooks for callbacks inside the server can be used.

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes (replicated cache)

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.