DBMS > Coveo vs. Databricks vs. ObjectBox vs. Realm vs. SQLite

System Properties Comparison Coveo vs. Databricks vs. ObjectBox vs. Realm vs. SQLite

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

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

Primary database model

Search engine

Document store
Relational DBMS

Object oriented DBMS
Vector DBMS

Document store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	2.14
Rank	#116	Overall
	#11	Search engines

Score	84.24
Rank	#14	Overall
	#2	Document stores
	#9	Relational DBMS

Score	1.08
Rank	#179	Overall
	#6	Object oriented DBMS
	#9	Vector DBMS

Score	7.18
Rank	#52	Overall
	#8	Document stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.coveo.com

www.databricks.com

github.com/objectbox
objectbox.io

realm.io

www.sqlite.org

Technical documentation

www.sqlite.org/docs.html

Developer

Coveo

Databricks

ObjectBox Limited

Realm, acquired by MongoDB in May 2019

Dwayne Richard Hipp

Initial release

2012

2013

2017

2014

2000

Current release

4.0 (May 2024)

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Bindings are released under Apache 2.0

Apache License 2.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

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

hosted

Android
Any POSIX system
Docker
iOS
Linux
macOS
QNX
Windows

Android
Backend: server-less
iOS
Windows

server-less

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

with Databricks SQL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Java
JavaScript
Python

Python
R
Scala

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

Server-side scripts

Stored procedures

user defined functions and aggregates

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

granular access controls, API key management, content filters

yes

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

News

MongoDB Realm & Device Sync alternatives – ObjectBox
17 September 2024

Local AI – what it is and why we need it
11 September 2024

First on-device Vector Database (aka Semantic Index) for iOS
24 July 2024

Retrieval Augmented Generation (RAG) with vector databases: Expanding AI Capabilities
18 June 2024

The on-device Vector Database for Android and Java
29 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.