DBMS > Blueflood vs. CouchDB vs. Snowflake vs. Tibero

System Properties Comparison Blueflood vs. CouchDB vs. Snowflake vs. Tibero

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 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 secure RDBMS, designed for easy portability from Oracle

Primary database model

Time Series DBMS

Document store

Relational DBMS

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	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

blueflood.io

couchdb.apache.org

www.snowflake.com

us.tmaxsoft.com/products/tibero

Technical documentation

github.com/rax-maas/blueflood/wiki

docs.couchdb.org/en/stable

docs.snowflake.net/manuals/index.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Rackspace

Apache Software Foundation

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

Snowflake Computing Inc.

TmaxSoft

Initial release

2013

2005

2014

2003

Current release

3.3.3, December 2023

6, April 2015

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2

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

Erlang

C and Assembler

Server operating systems

Linux
OS X

Android
BSD
Linux
OS X
Solaris
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

predefined scheme

schema-free

yes

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

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

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP REST

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

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
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

Persistent Stored Procedure (PSM)

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

improved architecture with release 2.0

yes

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

yes

Multi-source replication
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

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

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.

planned for next version

User concepts

Access control

Access rights for users can be defined per database

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.