DBMS > DolphinDB vs. Graph Engine vs. Infobright vs. Snowflake

System Properties Comparison DolphinDB vs. Graph Engine vs. Infobright vs. Snowflake

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.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

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

Primary database model

Time Series DBMS

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Relational DBMS

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

Score	4.03
Rank	#78	Overall
	#6	Time Series DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.dolphindb.com

www.graphengine.io

ignitetech.com/softwarelibrary/infobrightdb

www.snowflake.com

Technical documentation

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

www.graphengine.io/docs/manual

docs.snowflake.net/manuals/index.html

Developer

DolphinDB, Inc

Microsoft

Ignite Technologies Inc.; formerly InfoBright Inc.

Snowflake Computing Inc.

Initial release

2018

2010

2005

2014

Current release

v2.00.4, January 2022

License

Commercial or Open Source

commercial

free community version available

Open Source

MIT License

commercial

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

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

.NET and C

Server operating systems

Linux
Windows

.NET

Linux
Windows

hosted

Data scheme

yes

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

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

Knowledge Grid Technology used instead

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

RESTful HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

C#
C++
F#
Visual Basic

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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

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.