DBMS > Firebase Realtime Database vs. ObjectBox vs. Snowflake vs. VictoriaMetrics vs. Yanza

System Properties Comparison Firebase Realtime Database vs. ObjectBox vs. Snowflake vs. VictoriaMetrics 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.

Extremely fast embedded database for small devices, IoT and Mobile

Cloud-based data warehousing service for structured and semi-structured data

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Time Series DBMS for IoT Applications

Primary database model

Secondary database models

Time Series DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

firebase.google.com/products/realtime-database

objectbox.io

www.snowflake.com

victoriametrics.com

yanza.com

Technical documentation

firebase.google.com/docs/database

docs.objectbox.io

docs.snowflake.net/manuals/index.html

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Google

acquired by Google 2014

ObjectBox Limited

Snowflake Computing Inc.

VictoriaMetrics

Yanza

Initial release

2012

2017

2014

2018

2015

Current release

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

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 and C++

Server operating systems

hosted

Android
iOS
Linux
macOS
Windows

hosted

FreeBSD
Linux
macOS
OpenBSD

Windows

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

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

SQL

Support of SQL

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Proprietary native API

CLI Client
JDBC
ODBC

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

HTTP API

Supported programming languages

Java
JavaScript
Objective-C

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

JavaScript (Node.js)
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

Triggers

Callbacks are triggered when data changes

similar concept for controling cloud resources

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

online/offline synchronization between client and server

yes

Synchronous replication

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

Eventual Consistency

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

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.

User concepts

Access control

yes, based on authentication and database rules

yes

Users with fine-grained authorization concept, user roles and pluggable authentication

More information provided by the system vendor

News

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

Vector Database Release for Flutter / Dart + Python
13 June 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.