DBMS > EJDB vs. HarperDB vs. ObjectBox vs. SQLite

System Properties Comparison EJDB vs. HarperDB vs. ObjectBox vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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.

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

Widely used embeddable, in-process RDBMS

Primary database model

Document 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.31
Rank	#296	Overall
	#44	Document stores

Score	0.60
Rank	#244	Overall
	#38	Document stores

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

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/Softmotions/ejdb

www.harperdb.io

github.com/objectbox
objectbox.io

www.sqlite.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

docs.harperdb.io/docs

docs.objectbox.io

www.sqlite.org/docs.html

Developer

Softmotions

HarperDB

ObjectBox Limited

Dwayne Richard Hipp

Initial release

2012

2017

2000

Current release

3.1, August 2021

4.0 (May 2024)

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

free community edition available

Bindings are released under Apache 2.0

Apache License 2.0

Open Source

Public Domain

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

C and C++

Server operating systems

server-less

Linux
OS X

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

server-less

Data scheme

schema-free

dynamic schema

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON data types

yes, plus "flex" map-like 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

yes

SQL-92 is not fully supported

APIs and other access methods

in-process shared library

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.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

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

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

the nodes on which a table resides can be defined

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

none

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

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

yes

via file-system locks

Durability

Support for making data persistent

yes

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

yes

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.