DBMS > Blueflood vs. Datomic vs. RocksDB vs. Teradata Aster vs. Vitess

System Properties Comparison Blueflood vs. Datomic vs. RocksDB vs. Teradata Aster vs. Vitess

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Scalable TimeSeries DBMS based on Cassandra

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Platform for big data analytics on multistructured data sources and types

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

docs.datomic.com

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Rackspace

Cognitect

Facebook, Inc.

Teradata

The Linux Foundation, PlanetScale

Initial release

2013

2012

2013

2005

2013

Current release

1.0.6735, June 2023

9.2.1, May 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

limited edition free

Open Source

BSD

commercial

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java, Clojure

C++

Server operating systems

Linux
OS X

All OS with a Java VM

Linux

Docker
Linux
macOS

Data scheme

predefined scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

yes

Typing

predefined data types such as float or date

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

HTTP REST

RESTful HTTP API

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Clojure
Java

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
Python
R

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

R packages

yes

proprietary syntax

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

But extensive use of caching in the application peers

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

But extensive use of caching in the application peers

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.