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

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

Editorial information provided by DB-Engines

Name

Description

Scalable Time Series DBMS based on HBase

A fully ACID in-memory object graph database

Widely used embeddable, in-process RDBMS

Object-relational database and reports server

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Time Series DBMS

Document store
Object oriented DBMS

Relational DBMS

Document store

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	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

origodb.com/docs

www.sqlite.org/docs.html

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

www.xtdb.com/docs

Developer

currently maintained by Yahoo and other contributors

Robert Friberg et al

Dwayne Richard Hipp

Paradigma Software

Juxt Ltd.

Initial release

2011

2009

under the name LiveDB

2000

1999

2019

Current release

3.46.0 (23 May 2024), May 2024

5.7.5

1.19, September 2021

License

Commercial or Open Source

Open Source

LGPL

Open Source

Public Domain

commercial

Open Source

MIT License

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

Clojure

Server operating systems

Linux
Windows

server-less

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

dynamic column types

yes

schema-free

Typing

predefined data types such as float or date

numeric data for metrics, strings for tags

User defined using .NET types and collections

yes

not rigid because of 'dynamic typing' concept.

yes

yes, extensible-data-notation format

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

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP API
Telnet API

.NET Client API
HTTP API
LINQ

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ODBC

HTTP REST
JDBC

Supported programming languages

Erlang
Go
Java
Python
R
Ruby

.Net

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

Clojure
Java

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on HBase

Source-replica replication

none

yes, each node contains all data

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

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

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.