DBMS > Firebase Realtime Database vs. OrigoDB vs. SWC-DB vs. XTDB vs. Yanza

System Properties Comparison Firebase Realtime Database vs. OrigoDB vs. SWC-DB vs. XTDB vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is 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.

A fully ACID in-memory object graph database

A high performance, scalable Wide Column DBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Time Series DBMS for IoT Applications

Primary database model

Document store

Document store
Object oriented DBMS

Wide column store

Document store

Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

firebase.google.com/products/realtime-database

origodb.com

github.com/kashirin-alex/swc-db
www.swcdb.org

github.com/xtdb/xtdb
www.xtdb.com

yanza.com

Technical documentation

firebase.google.com/docs/database

origodb.com/docs

www.xtdb.com/docs

Developer

Google

acquired by Google 2014

Robert Friberg et al

Alex Kashirin

Juxt Ltd.

Yanza

Initial release

2012

2009

under the name LiveDB

2020

2019

2015

Current release

0.5, April 2021

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPL V3

Open Source

MIT License

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Clojure

Server operating systems

hosted

Linux
Windows

Linux

All OS with a Java 8 (and higher) VM
Linux

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes, extensible-data-notation format

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

limited SQL, making use of Apache Calcite

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

.NET Client API
HTTP API
LINQ

Proprietary protocol
Thrift

HTTP REST
JDBC

HTTP API

Supported programming languages

Java
JavaScript
Objective-C

.Net

C++

Clojure
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

Triggers

Callbacks are triggered when data changes

yes

Domain Events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, each node contains all data

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

depending on model

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

yes, based on authentication and database rules

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Atos cybersecurity blog: Misconfigured Firebase: A real-time cyber threat
18 January 2024, Atos

Don't be like these 900+ websites and expose millions of passwords via Firebase
18 March 2024, The Register

Google launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

Google Firebase may have exposed 125M records from misconfigurations
19 March 2024, SC Media

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page