DBMS > Amazon Redshift vs. Apache Impala vs. Drizzle vs. GeoMesa vs. KairosDB

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Drizzle vs. GeoMesa vs. KairosDB

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

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for Hadoop

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Distributed Time Series DBMS based on Cassandra or H2

Primary database model

Relational DBMS

Spatial DBMS

Time Series DBMS

Secondary database models

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Website

aws.amazon.com/redshift

impala.apache.org

www.geomesa.org

github.com/kairosdb/kairosdb

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

www.geomesa.org/documentation/stable/user/index.html

kairosdb.github.io

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Drizzle project, originally started by Brian Aker

CCRi and others

Initial release

2012

2013

2008

2014

2013

Current release

4.1.0, June 2022

7.2.4, September 2012

5.0.0, May 2024

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GNU GPL

Open Source

Apache License 2.0

Open Source

Apache 2.0

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++

Scala

Java

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X

Linux
OS X
Windows

Data scheme

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JDBC

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication
Source-replica replication

depending on storage layer

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

depending on storage layer

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

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

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

depending on the DBMS used for storage

simple password-based access control

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.