DBMS > BigObject vs. ObjectBox vs. Realm vs. SQLite vs. Teradata

System Properties Comparison BigObject vs. ObjectBox vs. Realm vs. SQLite vs. Teradata

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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

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

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Object oriented DBMS
Vector DBMS

Document store

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

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

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

bigobject.io

github.com/objectbox
objectbox.io

realm.io

www.sqlite.org

www.teradata.com

Technical documentation

docs.bigobject.io

docs.objectbox.io

realm.io/docs

www.sqlite.org/docs.html

docs.teradata.com

Developer

BigObject, Inc.

ObjectBox Limited

Realm, acquired by MongoDB in May 2019

Dwayne Richard Hipp

Teradata

Initial release

2015

2017

2014

2000

1984

Current release

4.0 (May 2024)

3.46.0 (23 May 2024), May 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

free community edition available

Bindings are released under Apache 2.0

Apache License 2.0

Open Source

Public Domain

commercial

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

C and C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

Android
Backend: server-less
iOS
Windows

server-less

hosted
Linux

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.

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

yes

SQL 2016 + extensions

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C
C++
Dart (Flutter)
Go
Java
Kotlin
Python
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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

Lua

runs within the applications so server-side scripts are unnecessary

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

via file-system locks

yes

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

yes

fine grained access rights according to SQL-standard

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.