DBMS > DolphinDB vs. FatDB vs. Google BigQuery vs. IBM Cloudant

System Properties Comparison DolphinDB vs. FatDB vs. Google BigQuery vs. IBM Cloudant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Large scale data warehouse service with append-only tables

Database as a Service offering based on Apache CouchDB

Primary database model

Time Series DBMS

Document store
Key-value store

Relational DBMS

Document store

Secondary database models

Relational DBMS

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

Score	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Website

www.dolphindb.com

cloud.google.com/bigquery

www.ibm.com/products/cloudant

Technical documentation

docs.dolphindb.cn/en/help200/index.html

cloud.google.com/bigquery/docs

cloud.ibm.com/docs/Cloudant

Developer

DolphinDB, Inc

FatCloud

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2018

2012

2010

Current release

v2.00.4, January 2022

License

Commercial or Open Source

commercial

free community version available

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

C++

Erlang

Server operating systems

Linux
Windows

Windows

hosted

Data scheme

yes

schema-free

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

Via inetgration in SQL Server

yes

APIs and other access methods

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

Supported programming languages

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

yes

via applications

user defined functions

in JavaScript

View functions (Map-Reduce) in JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Since BigQuery is designed for querying data

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

yes

User concepts

Access control

Administrators, Users, Groups

Can implement custom security layer via applications

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

Google Cloud Identity & Access Management (IAM)

Access rights for users can be defined per database

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.