DBMS > DolphinDB vs. FatDB vs. gStore vs. Infobright

System Properties Comparison DolphinDB vs. FatDB vs. gStore vs. Infobright

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.

A native Graph DBMS to store and maintain very large RDF datasets.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Primary database model

Time Series DBMS

Document store
Key-value store

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Relational DBMS

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

Score	4.23
Rank	#82	Overall
	#6	Time Series DBMS

Score	0.05
Rank	#371	Overall
	#39	Graph DBMS
	#18	RDF stores

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Website

www.dolphindb.com

en.gstore.cn

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

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

en.gstore.cn/#/enDocs

Developer

DolphinDB, Inc

FatCloud

Ignite Technologies Inc.; formerly InfoBright Inc.

Initial release

2018

2012

2016

2005

Current release

v2.00.4, January 2022

1.2, November 2023

License

Commercial or Open Source

commercial

free community version available

commercial

Open Source

BSD

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Cloud-based only

Only available as a cloud service

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

Windows

Linux

Linux
Windows

Data scheme

yes

schema-free

schema-free and OWL/RDFS-schema support

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.

Secondary indexes

yes

Knowledge Grid Technology used instead

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

HTTP API
SPARQL 1.1

ADO.NET
JDBC
ODBC

Supported programming languages

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

C++
Java
JavaScript (Node.js)
PHP
Python

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via applications

yes

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

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

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

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.

yes

User concepts

Access control

Administrators, Users, Groups

Can implement custom security layer via applications

Users, roles and permissions, Role-Based Access Control (RBAC) supported

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

Share this page