DBMS > Apache Phoenix vs. ObjectBox vs. Realm vs. SQLite vs. Vitess

System Properties Comparison Apache Phoenix vs. ObjectBox vs. Realm vs. SQLite vs. Vitess

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Extremely fast embedded database for small devices, IoT and Mobile

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Widely used embeddable, in-process RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	1.29
Rank	#166	Overall
	#5	Object oriented DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

Technical documentation

phoenix.apache.org

docs.objectbox.io

realm.io/docs

www.sqlite.org/docs.html

vitess.io/docs

Developer

Apache Software Foundation

ObjectBox Limited

Realm, acquired by MongoDB in May 2019

Dwayne Richard Hipp

The Linux Foundation, PlanetScale

Initial release

2014

2017

2014

2000

2013

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

3.46.0 (23 May 2024), May 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

Public Domain

Open Source

Apache Version 2.0, commercial licenses available

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

C and C++

Server operating systems

Linux
Unix
Windows

Android
iOS
Linux
macOS
Windows

Android
Backend: server-less
iOS
Windows

server-less

Docker
Linux
macOS

Data scheme

yes

late-bound, schema-on-read capabilities

yes

dynamic column types

yes

Typing

predefined data types such as float or date

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

with proprietary extensions

APIs and other access methods

JDBC

Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

.Net
Java

with Android only
Objective-C
React Native
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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

runs within the applications so server-side scripts are unnecessary

yes

proprietary syntax

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

online/offline synchronization between client and server

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

In-Memory realm

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

yes

Users with fine-grained authorization concept

no user groups or roles

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.