DBMS > Amazon DynamoDB vs. Blueflood vs. GridDB vs. Tarantool vs. TimescaleDB

System Properties Comparison Amazon DynamoDB vs. Blueflood vs. GridDB vs. Tarantool vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Scalable TimeSeries DBMS based on Cassandra

Scalable in-memory time series database optimized for IoT and Big Data

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Document store
Key-value store

Time Series DBMS

Document store
Key-value store
Relational DBMS

Time Series DBMS

Secondary database models

Key-value store
Relational DBMS

Spatial DBMS

with Tarantool/GIS extension

Relational DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

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

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

github.com/rax-maas/blueflood/wiki

docs.griddb.net

www.tarantool.io/en/doc

docs.timescale.com

Developer

Amazon

Rackspace

Toshiba Corporation

Timescale

Initial release

2012

2013

2008

2017

Current release

5.1, August 2022

2.10.0, May 2022

2.15.0, May 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

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

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

Java

C++

C and C++

Server operating systems

hosted

Linux
OS X

Linux

BSD
Linux
macOS

Linux
OS X
Windows

Data scheme

schema-free

predefined scheme

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

numerical, string, blob, geometry, boolean, timestamp

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

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

Secondary indexes

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

Full-featured ANSI SQL support

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP API

HTTP REST

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Open binary protocol

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

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Lua, C and SQL stored procedures

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

by integration with AWS Lambda

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

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

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

Source-replica replication

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

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate consistency within container, eventual consistency across containers

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

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID at container level

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

ACID

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Access rights for users can be defined per database

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

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.