DBMS > DolphinDB vs. Qdrant vs. SQLite vs. VictoriaMetrics

System Properties Comparison DolphinDB vs. Qdrant vs. SQLite vs. VictoriaMetrics

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 high-performance vector database with neural network or semantic-based matching

Widely used embeddable, in-process RDBMS

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

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	1.28
Rank	#167	Overall
	#7	Vector DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

www.dolphindb.com

github.com/qdrant/qdrant
qdrant.tech

www.sqlite.org

victoriametrics.com

Technical documentation

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

qdrant.tech/documentation

www.sqlite.org/docs.html

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

DolphinDB, Inc

Qdrant

Dwayne Richard Hipp

VictoriaMetrics

Initial release

2018

2021

2000

2018

Current release

v2.00.4, January 2022

3.46.0 (23 May 2024), May 2024

v1.91, May 2023

License

Commercial or Open Source

commercial

free community version available

Open Source

Apache Version 2.0

Open Source

Public Domain

Open Source

Apache Version 2.0

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

Rust

Server operating systems

Linux
Windows

Docker
Linux
macOS
Windows

server-less

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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.

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

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
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Collection-level replication

none

Synchronous 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, tunable consistency

Eventual 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

via file-system locks

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

Key-based 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.