DBMS > Firebase Realtime Database vs. GeoSpock vs. Oracle vs. Realm

System Properties Comparison Firebase Realtime Database vs. GeoSpock vs. Oracle vs. Realm

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Spatial and temporal data processing engine for extreme data scale

Widely used RDBMS

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

Primary database model

Document store

Relational DBMS

Document store

Secondary database models

Time Series DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Website

firebase.google.com/products/realtime-database

geospock.com

www.oracle.com/database

realm.io

Technical documentation

firebase.google.com/docs/database

docs.oracle.com/en/database

realm.io/docs

Developer

Google

acquired by Google 2014

GeoSpock

Oracle

Realm, acquired by MongoDB in May 2019

Initial release

2012

1980

2014

Current release

2.0, September 2019

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

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, Javascript

C and C++

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Android
Backend: server-less
iOS
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JDBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

limited functionality with using 'rules'

PL/SQL

also stored procedures in Java possible

runs within the applications so server-side scripts are unnecessary

Triggers

Callbacks are triggered when data changes

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

In-Memory realm

User concepts

Access control

yes, based on authentication and database rules

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

yes

More information provided by the system vendor

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.