DBMS > Graph Engine vs. ObjectBox vs. SQLite vs. VoltDB

System Properties Comparison Graph Engine vs. ObjectBox vs. SQLite vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Lightweight, fast on-device database for IoT, Mobile and Embedded devices, persisting and synchronising objects and vectors

Widely used embeddable, in-process RDBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Graph DBMS
Key-value store

Object oriented DBMS
Vector DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.29
Rank	#166	Overall
	#5	Object oriented DBMS
	#7	Vector DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.graphengine.io

github.com/objectbox
objectbox.io

www.sqlite.org

www.voltdb.com

Technical documentation

www.graphengine.io/docs/manual

docs.objectbox.io

www.sqlite.org/docs.html

docs.voltdb.com

Developer

Microsoft

ObjectBox Limited

Dwayne Richard Hipp

VoltDB Inc.

Initial release

2010

2017

2000

2010

Current release

4.0 (May 2024)

3.46.0 (23 May 2024), May 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

MIT License

Bindings are released under Apache 2.0

Apache License 2.0

Open Source

Public Domain

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

.NET and C

C and C++

Java, C++

Server operating systems

.NET

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

server-less

Linux
OS X

for development

Data scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

yes, plus "flex" map-like types

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP API

Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
C++
F#
Visual Basic

C
C++
Dart (Flutter)
Go
Java
Kotlin
Python
Swift

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Data sync between devices allowing occasional connected databases to work completely offline

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Data access is serialized by the server

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

yes

Users and roles with access to stored procedures

More information provided by the system vendor

News

The on-device Vector Database for Android and Java
29 May 2024

Vector search: making sense of search queries
29 May 2024

Python on-device Vector and Object Database for Local AI
28 May 2024

Evolution of search: traditional vs vector search
23 May 2024

On-device Vector Database for Dart/Flutter
21 May 2024

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.