DBMS > 4D vs. Apache Druid vs. Geode vs. RocksDB vs. Teradata Aster

System Properties Comparison 4D vs. Apache Druid vs. Geode vs. RocksDB vs. Teradata Aster

Editorial information provided by DB-Engines

Name

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

Description

Application development environment with integrated database management system

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Relational DBMS
Time Series DBMS

Key-value store

Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

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

Website

Technical documentation

developer.4d.com

druid.apache.org/docs/latest/design

geode.apache.org/docs

github.com/facebook/rocksdb/wiki

Developer

4D, Inc

Apache Software Foundation and contributors

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Facebook, Inc.

Teradata

Initial release

1984

2012

2002

2013

2005

Current release

v20, April 2023

29.0.1, April 2024

1.1, February 2017

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

C++

Server operating systems

OS X
Windows

Linux
OS X
Unix

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

yes

schema-less columns are supported

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

close to SQL 92

SQL for querying

SQL-like query language (OQL)

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
RESTful HTTP/JSON API

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

4D proprietary IDE
PHP

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

user defined functions

R packages

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, via HDFS, S3 or other storage engines

Multi-source replication

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

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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, on a single node

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

Users and groups

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

Access rights per client and object definable

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.