DBMS > Amazon Redshift vs. etcd vs. GeoSpock vs. IRONdb vs. Postgres-XL

System Properties Comparison Amazon Redshift vs. etcd vs. GeoSpock vs. IRONdb vs. Postgres-XL

Editorial information provided by DB-Engines

Name

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

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

A distributed reliable key-value store

Spatial and temporal data processing engine for extreme data scale

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

aws.amazon.com/redshift

etcd.io
github.com/etcd-io/etcd

geospock.com

www.circonus.com/solutions/time-series-database/

www.postgres-xl.org

Technical documentation

docs.aws.amazon.com/redshift

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.circonus.com/irondb/category/getting-started

www.postgres-xl.org/documentation

Developer

Amazon (based on PostgreSQL)

GeoSpock

Circonus LLC.

Initial release

2012

2017

2014

since 2012, originally named StormDB

Current release

3.4, August 2019

2.0, September 2019

V0.10.20, January 2018

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Mozilla public 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, Javascript

C and C++

Server operating systems

hosted

FreeBSD
Linux
Windows

experimental

hosted

Linux

Linux
macOS

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

XML type, but no XML query functionality

Secondary indexes

restricted

temporal, categorical

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI SQL for query only (using Presto)

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

distributed, parallel query execution

APIs and other access methods

JDBC
ODBC

gRPC
JSON over HTTP

JDBC

HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes, in Lua

user defined functions

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Automatic, metric affinity per node

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

configurable replication factor, datacenter aware

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

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

MVCC

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

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

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.