DBMS > Blueflood vs. etcd vs. Google BigQuery vs. Microsoft Azure Cosmos DB

System Properties Comparison Blueflood vs. etcd vs. Google BigQuery vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

A distributed reliable key-value store

Large scale data warehouse service with append-only tables

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

blueflood.io

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

cloud.google.com/bigquery

azure.microsoft.com/services/cosmos-db

Technical documentation

github.com/rax-maas/blueflood/wiki

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

cloud.google.com/bigquery/docs

learn.microsoft.com/azure/cosmos-db

Developer

Rackspace

Google

Microsoft

Initial release

2013

2010

2014

Current release

3.4, August 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

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

Server operating systems

Linux
OS X

FreeBSD
Linux
Windows

experimental

hosted

Data scheme

predefined scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON 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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

HTTP REST

gRPC
JSON over HTTP

RESTful HTTP/JSON API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

JavaScript

Triggers

yes, watching key changes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

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

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

Multi-item ACID transactions with snapshot isolation within a partition

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.

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights can be defined down to the item level

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.