DBMS > HarperDB vs. OrientDB vs. SQLite vs. VictoriaMetrics

System Properties Comparison HarperDB vs. OrientDB vs. SQLite vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Multi-model DBMS (Document, Graph, Key/Value)

Widely used embeddable, in-process RDBMS

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

Primary database model

Document store

Document store
Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

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

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

Technical documentation

docs.harperdb.io/docs

www.orientdb.com/docs/last/index.html

www.sqlite.org/docs.html

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

Developer

HarperDB

OrientDB LTD; CallidusCloud; SAP

Dwayne Richard Hipp

VictoriaMetrics

Initial release

2017

2010

2000

2018

Current release

3.1, August 2021

3.2.29, March 2024

3.45.3 (15 April 2024), April 2024

v1.91, May 2023

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache version 2

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

Node.js

Java

Server operating systems

Linux
OS X

All OS with a Java JDK (>= JDK 6)

server-less

FreeBSD
Linux
macOS
OpenBSD

Data scheme

dynamic schema

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

dynamic column types

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL

Support of SQL

SQL-like data manipulation statements

SQL-like query language, no joins

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

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

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

Custom Functions

since release 3.1

Java, Javascript

Triggers

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

A table resides as a whole on one (or more) nodes in a cluster

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

Multi-source replication

none

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes, using LMDB

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

Access rights for users and roles

Access rights for users and roles; record level security configurable

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.