DBMS > DolphinDB vs. Ignite vs. Kinetica vs. SQLite

System Properties Comparison DolphinDB vs. Ignite vs. Kinetica 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.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Fully vectorized database across both GPUs and CPUs

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	4.03
Rank	#78	Overall
	#6	Time Series DBMS

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

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

apacheignite.readme.io/docs

docs.kinetica.com

www.sqlite.org/docs.html

Developer

DolphinDB, Inc

Apache Software Foundation

Kinetica

Dwayne Richard Hipp

Initial release

2018

2015

2012

2000

Current release

v2.00.4, January 2022

Apache Ignite 2.6

7.1, August 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

free community version available

Open Source

Apache 2.0

commercial

Open Source

Public Domain

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

C++, Java, .Net

C, C++

Server operating systems

Linux
Windows

Linux
OS X
Solaris
Windows

Linux

server-less

Data scheme

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

ANSI-99 for query and DML statements, subset of DDL

SQL-like DML and DDL statements

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java
JavaScript (Node.js)
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

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes (cache interceptors and events)

yes

triggers when inserted values for one or more columns fall within a specified range

yes

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

yes (replicated cache)

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

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

GPU vRAM or System RAM

yes

User concepts

Access control

Administrators, Users, Groups

Security Hooks for custom implementations

Access rights for users and roles on table 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.