DBMS > OpenTSDB vs. OrigoDB vs. Qdrant vs. SQLite vs. Valentina Server

System Properties Comparison OpenTSDB vs. OrigoDB vs. Qdrant vs. SQLite vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

Scalable Time Series DBMS based on HBase

A fully ACID in-memory object graph database

A high-performance vector database with neural network or semantic-based matching

Widely used embeddable, in-process RDBMS

Object-relational database and reports server

Primary database model

Time Series DBMS

Document store
Object oriented DBMS

Vector DBMS

Relational DBMS

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

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

opentsdb.net

origodb.com

github.com/qdrant/qdrant
qdrant.tech

www.sqlite.org

www.valentina-db.net

Technical documentation

opentsdb.net/docs/build/html/index.html

origodb.com/docs

qdrant.tech/documentation

www.sqlite.org/docs.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

currently maintained by Yahoo and other contributors

Robert Friberg et al

Qdrant

Dwayne Richard Hipp

Paradigma Software

Initial release

2011

2009

under the name LiveDB

2021

2000

1999

Current release

3.46.0 (23 May 2024), May 2024

5.7.5

License

Commercial or Open Source

Open Source

LGPL

Open Source

Apache Version 2.0

Open Source

Public Domain

commercial

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

Java

Rust

Server operating systems

Linux
Windows

Docker
Linux
macOS
Windows

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

numeric data for metrics, strings for tags

User defined using .NET types and collections

Numbers, Strings, Geo, Boolean

yes

not rigid because of 'dynamic typing' concept.

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.

can be achieved using .NET

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

APIs and other access methods

HTTP API
Telnet API

.NET Client API
HTTP API
LINQ

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC

Supported programming languages

Erlang
Go
Java
Python
R
Ruby

.Net

.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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

horizontal partitioning

client side managed; servers are not synchronized

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on HBase

Source-replica replication

Collection-level replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

Key-based authentication

fine grained access rights according to SQL-standard

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.