DBMS > Google Cloud Firestore vs. H2GIS vs. LevelDB vs. ObjectBox vs. SQLite

System Properties Comparison Google Cloud Firestore vs. H2GIS vs. LevelDB vs. ObjectBox vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Spatial extension of H2

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Extremely fast embedded database for small devices, IoT and Mobile

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

Time Series DBMS

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

firebase.google.com/products/firestore

www.h2gis.org

github.com/google/leveldb

objectbox.io

www.sqlite.org

Technical documentation

firebase.google.com/docs/firestore

www.h2gis.org/docs/home

github.com/google/leveldb/blob/main/doc/index.md

docs.objectbox.io

www.sqlite.org/docs.html

Developer

Google

CNRS

Google

ObjectBox Limited

Dwayne Richard Hipp

Initial release

2017

2013

2011

2017

2000

Current release

1.23, February 2021

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

Open Source

BSD

Open Source

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

Java

C++

C and C++

Server operating systems

hosted

Illumos
Linux
OS X
Windows

Android
iOS
Linux
macOS
Windows

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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

yes

SQL-92 is not fully supported

APIs and other access methods

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Java

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
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

yes, Firebase Rules & Cloud Functions

yes

based on H2

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

based on H2

none

online/offline synchronization between client and server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

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

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

yes

with automatic compression on writes

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, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

yes

based on H2

yes

More information provided by the system vendor

News

The first On-Device Vector Database: ObjectBox 4.0
16 May 2024

Edge AI: The era of on-device AI
23 April 2024

In-Memory Database Use Cases
15 February 2024

Data Viewer for Objects – announcing ObjectBox Admin
14 November 2023

Vector Databases for Edge AI
9 August 2023

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.