DBMS > DolphinDB vs. Google Cloud Bigtable vs. OpenQM vs. SQLite

System Properties Comparison DolphinDB vs. Google Cloud Bigtable vs. OpenQM vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

QpenQM is a high-performance, self-tuning, multi-value DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Key-value store
Wide column store

Multivalue DBMS

Relational DBMS

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	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.dolphindb.com

cloud.google.com/bigtable

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.sqlite.org

Technical documentation

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

cloud.google.com/bigtable/docs

www.sqlite.org/docs.html

Developer

DolphinDB, Inc

Google

Rocket Software, originally Martin Phillips

Dwayne Richard Hipp

Initial release

2018

2015

1993

2000

Current release

v2.00.4, January 2022

3.4-12

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

free community version available

commercial

Open Source

GPLv2, extended commercial license available

Open Source

Public Domain

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++

Server operating systems

Linux
Windows

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

server-less

Data scheme

yes

schema-free

yes

with some exceptions

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

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

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C#
C++
Go
Java
JavaScript (Node.js)
Python

.Net
Basic
C
Java
Objective C
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights can be defined down to the item level

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.