DBMS > Amazon Redshift vs. Apache Druid vs. GeoSpock vs. Tarantool vs. Transbase

System Properties Comparison Amazon Redshift vs. Apache Druid vs. GeoSpock vs. Tarantool vs. Transbase

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

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

Spatial and temporal data processing engine for extreme data scale

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

aws.amazon.com/redshift

druid.apache.org

geospock.com

www.tarantool.io

www.transaction.de/en/products/transbase.html

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

www.tarantool.io/en/doc

www.transaction.de/en/products/transbase/features.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

GeoSpock

Transaction Software GmbH

Initial release

2012

2008

1987

Current release

29.0.1, April 2024

2.0, September 2019

2.10.0, May 2022

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

free development license

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

Java

Java, Javascript

C and C++

Server operating systems

hosted

Linux
OS X
Unix

hosted

BSD
Linux
macOS

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-less columns are supported

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

temporal, categorical

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL for querying

ANSI SQL for query only (using Presto)

Full-featured ANSI SQL support

yes

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

JDBC

Open binary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Lua, C and SQL stored procedures

yes

Triggers

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Automatic sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency

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

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

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

Access rights for users can be defined per table

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.