DBMS > CouchDB vs. Firebird vs. GridDB vs. Snowflake vs. Tarantool

System Properties Comparison CouchDB vs. Firebird vs. GridDB vs. Snowflake vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

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

Firebird is an open source RDBMS forked from Borland's InterBase

Scalable in-memory time series database optimized for IoT and Big Data

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Key-value store
Relational DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

Technical documentation

docs.couchdb.org/en/stable

www.firebirdsql.org/en/reference-manuals

docs.griddb.net

docs.snowflake.net/manuals/index.html

www.tarantool.io/en/doc

Developer

Apache Software Foundation

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

Firebird Foundation

Toshiba Corporation

Snowflake Computing Inc.

Initial release

2005

2000

As fork of Borland's InterBase

2013

2014

2008

Current release

3.3.3, December 2023

5.0.0, January 2024

5.1, August 2022

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Initial Developer's Public License

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

Erlang

C and C++

C++

C and C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux

hosted

BSD
Linux
macOS

Data scheme

schema-free

yes

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

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

SQL92, SQL-like TQL (Toshiba Query Language)

yes

Full-featured ANSI SQL support

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Open binary protocol

Supported programming languages

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

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

View functions in JavaScript

PSQL

user defined functions

Lua, C and SQL stored procedures

Triggers

yes

similar concept for controling cloud resources

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

Sharding

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

ACID at container level

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights for users can be defined per database

Users with fine-grained authorization concept

Access rights for users can be defined per database

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.