DBMS > Apache Drill vs. Atos Standard Common Repository vs. Geode vs. RocksDB vs. SpaceTime

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. Geode vs. RocksDB vs. SpaceTime

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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)

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Key-value store

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

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

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

drill.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

geode.apache.org

rocksdb.org

www.mireo.com/spacetime

Technical documentation

drill.apache.org/docs

geode.apache.org/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Atos Convergence Creators

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

Facebook, Inc.

Mireo

Initial release

2012

2016

2002

2013

2020

Current release

1.20.3, January 2023

1703

1.1, February 2017

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

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

Linux
OS X
Windows

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

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

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language (OQL)

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

RESTful HTTP API

Supported programming languages

C++

All languages with LDAP bindings

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

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

yes, on a single node

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

LDAP bind authentication

Access rights per client and object definable

yes

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.