DBMS > Blueflood vs. CouchDB vs. Snowflake vs. TigerGraph vs. ToroDB

System Properties Comparison Blueflood vs. CouchDB vs. Snowflake vs. TigerGraph 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.

Cloud-based data warehousing service for structured and semi-structured data

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

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.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

github.com/torodb/server

Technical documentation

github.com/rax-maas/blueflood/wiki

docs.couchdb.org/en/stable

docs.snowflake.net/manuals/index.html

docs.tigergraph.com

Developer

Rackspace

Apache Software Foundation

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

Snowflake Computing Inc.

8Kdata

Initial release

2013

2005

2014

2017

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

C++

Java

Server operating systems

Linux
OS X

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux

All OS with a Java 7 VM

Data scheme

predefined scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

via views

SQL

Support of SQL

yes

SQL-like query language (GSQL)

APIs and other access methods

HTTP REST

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

improved architecture with release 2.0

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

yes

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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 rights for users can be defined per database

Users with fine-grained authorization concept, user roles and pluggable authentication

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