DBMS > Amazon DocumentDB vs. Amazon Redshift vs. Drizzle vs. Geode vs. Kinetica

System Properties Comparison Amazon DocumentDB vs. Amazon Redshift vs. Drizzle vs. Geode vs. Kinetica

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.

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Large scale data warehouse service for use with business intelligence tools

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

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

Fully vectorized database across both GPUs and CPUs

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Website

aws.amazon.com/documentdb

aws.amazon.com/redshift

geode.apache.org

www.kinetica.com

Technical documentation

aws.amazon.com/documentdb/resources

docs.aws.amazon.com/redshift

geode.apache.org/docs

docs.kinetica.com

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

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

Kinetica

Initial release

2019

2012

2008

2002

2012

Current release

7.2.4, September 2012

1.1, February 2017

7.1, August 2021

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

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

C++

Java

C, C++

Server operating systems

hosted

FreeBSD
Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

schema-free

yes

schema-free

yes

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

SQL-like query language (OQL)

SQL-like DML and DDL statements

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

All languages supporting JDBC/ODBC

C
C++
Java
PHP

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

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Multi-source replication
Source-replica replication

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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

typically not used, however similar functionality with DBRef possible

yes

informational only, not enforced by the system

yes

Transaction concepts

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

Atomic single-document operations

ACID

yes, on a single node

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

GPU vRAM or System RAM

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights per client and object definable

Access rights for users and roles on table level

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.