DBMS > Amazon Redshift vs. KairosDB vs. Lovefield vs. OpenTSDB vs. ToroDB

System Properties Comparison Amazon Redshift vs. KairosDB vs. Lovefield vs. OpenTSDB vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB 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

Distributed Time Series DBMS based on Cassandra or H2

Embeddable relational database for web apps written in pure JavaScript

Scalable Time Series DBMS based on HBase

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Website

aws.amazon.com/redshift

github.com/kairosdb/kairosdb

google.github.io/lovefield

opentsdb.net

github.com/torodb/server

Technical documentation

docs.aws.amazon.com/redshift

kairosdb.github.io

github.com/google/lovefield/blob/master/docs/spec_index.md

opentsdb.net/docs/build/html/index.html

Developer

Amazon (based on PostgreSQL)

Google

currently maintained by Yahoo and other contributors

8Kdata

Initial release

2012

2013

2014

2011

2016

Current release

1.2.2, November 2018

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

LGPL

Open Source

AGPL-V3

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

Java

Server operating systems

hosted

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

yes

string, integer, double, boolean, date, object_id

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 query language

via JavaScript builder pattern

APIs and other access methods

JDBC
ODBC

Graphite protocol
HTTP REST
Telnet API

HTTP API
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

Java
JavaScript

Node.js
PHP
Python

JavaScript

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Sharding

based on HBase

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

none

selectable replication factor

based on HBase

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

based on HBase

Eventual Consistency
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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

Access rights for users and roles

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.