DBMS > Blueflood vs. CouchDB vs. Google BigQuery vs. SQL.JS vs. ToroDB

System Properties Comparison Blueflood vs. CouchDB vs. Google BigQuery vs. SQL.JS vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Scalable TimeSeries DBMS based on Cassandra

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Large scale data warehouse service with append-only tables

Port of SQLite to JavaScript

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

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Website

blueflood.io

couchdb.apache.org

cloud.google.com/bigquery

sql.js.org

github.com/torodb/server

Technical documentation

github.com/rax-maas/blueflood/wiki

docs.couchdb.org/en/stable

cloud.google.com/bigquery/docs

sql.js.org/documentation/index.html

Developer

Rackspace

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Google

Alon Zakai

enhancements implemented by others

8Kdata

Initial release

2013

2005

2010

2012

2016

Current release

3.3.3, December 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2

commercial

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

Erlang

JavaScript

Java

Server operating systems

Linux
OS X

Android
BSD
Linux
OS X
Solaris
Windows

hosted

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

All OS with a Java 7 VM

Data scheme

predefined scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

yes

via views

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP REST

RESTful HTTP/JSON API

JavaScript API

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

improved architecture with release 2.0

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

except by serializing a db to a file

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

Access rights for users can be defined per database

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

Google Cloud Identity & Access Management (IAM)

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.