DBMS > Firebase Realtime Database vs. GridDB vs. Prometheus vs. SQLite vs. YTsaurus

System Properties Comparison Firebase Realtime Database vs. GridDB vs. Prometheus vs. SQLite vs. YTsaurus

Editorial information provided by DB-Engines

Name

Description

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

Scalable in-memory time series database optimized for IoT and Big Data

Open-source Time Series DBMS and monitoring system

Widely used embeddable, in-process RDBMS

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Document store

Time Series DBMS

Relational DBMS

Document store
Key-value store

Secondary database models

Key-value store
Relational DBMS

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

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	7.56
Rank	#49	Overall
	#3	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.15
Rank	#323	Overall
	#44	Document stores
	#47	Key-value stores

Website

firebase.google.com/products/realtime-database

Technical documentation

firebase.google.com/docs/database

docs.griddb.net

prometheus.io/docs

www.sqlite.org/docs.html

ytsaurus.tech/docs/en

Developer

Google

acquired by Google 2014

Toshiba Corporation

Dwayne Richard Hipp

Yandex

Initial release

2012

2013

2015

2000

2023

Current release

5.1, August 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

Apache License, Version 2.0

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

Server operating systems

hosted

Linux

Linux
Windows

server-less

Ubuntu

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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.

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

SQL-92 is not fully supported

YQL, an SQL-based language, is supported

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
JavaScript
Objective-C

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

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

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

by Federation

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

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 within container, eventual consistency across containers

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

User concepts

Access control

yes, based on authentication and database rules

Access rights for users can be defined per database

Access Control Lists

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.