DBMS > ArcadeDB vs. SQLite vs. VictoriaMetrics vs. XTDB

System Properties Comparison ArcadeDB vs. SQLite vs. VictoriaMetrics vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

Widely used embeddable, in-process RDBMS

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

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

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Time Series DBMS

Document store

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

Score	0.02
Rank	#366	Overall
	#50	Document stores
	#38	Graph DBMS
	#53	Key-value stores
	#36	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

arcadedb.com

www.sqlite.org

victoriametrics.com

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

Technical documentation

docs.arcadedb.com

www.sqlite.org/docs.html

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

www.xtdb.com/docs

Developer

Arcade Data

Dwayne Richard Hipp

VictoriaMetrics

Juxt Ltd.

Initial release

2021

2000

2018

2019

Current release

September 2021

3.46.0 (23 May 2024), May 2024

v1.91, May 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Public Domain

Open Source

Apache Version 2.0

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

All OS with a Java VM

server-less

FreeBSD
Linux
macOS
OpenBSD

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

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

HTTP REST
JDBC

Supported programming languages

Java

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

Clojure
Java

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Synchronous replication

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

Eventual Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

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

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.