DBMS > Amazon Redshift vs. BigObject vs. Citus vs. Graphite vs. SwayDB

System Properties Comparison Amazon Redshift vs. BigObject vs. Citus vs. Graphite vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for real-time computations and queries

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Time Series DBMS

Key-value store

Secondary database models

Document store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.13
Rank	#329	Overall
	#147	Relational DBMS

Score	2.13
Rank	#117	Overall
	#56	Relational DBMS

Score	5.19
Rank	#62	Overall
	#4	Time Series DBMS

Score	0.00
Rank	#384	Overall
	#60	Key-value stores

Website

aws.amazon.com/redshift

bigobject.io

www.citusdata.com

github.com/graphite-project/graphite-web

swaydb.simer.au

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

docs.citusdata.com

graphite.readthedocs.io

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

Chris Davis

Simer Plaha

Initial release

2012

2015

2010

2006

2018

Current release

8.1, December 2018

License

Commercial or Open Source

commercial

free community edition available

Open Source

AGPL, commercial license also available

Open Source

Apache 2.0

Open Source

GNU Affero GPL V3.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

Python

Scala

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux

Linux
Unix

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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

specific XML type available, but no XML query functionality

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

standard, with numerous extensions

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

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

HTTP API
Sockets

Supported programming languages

All languages supporting JDBC/ODBC

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

JavaScript (Node.js)
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

other methods possible by using 3rd party extensions

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

locking

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

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.