DBMS > Firebase Realtime Database vs. Microsoft SQL Server vs. Prometheus vs. ToroDB vs. YottaDB

System Properties Comparison Firebase Realtime Database vs. Microsoft SQL Server vs. Prometheus vs. ToroDB vs. YottaDB

Editorial information provided by DB-Engines

Name

ToroDB 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.

Microsofts flagship relational DBMS

Open-source Time Series DBMS and monitoring system

A MongoDB-compatible JSON document store, built on top of PostgreSQL

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

firebase.google.com/products/realtime-database

www.microsoft.com/en-us/sql-server

prometheus.io

github.com/torodb/server

yottadb.com

Technical documentation

firebase.google.com/docs/database

learn.microsoft.com/en-US/sql/sql-server

prometheus.io/docs

yottadb.com/resources/documentation

Developer

Google

acquired by Google 2014

Microsoft

8Kdata

YottaDB, LLC

Initial release

2012

1989

2015

2016

2001

Current release

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

AGPL-V3

Open Source

AGPL 3.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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Java

Server operating systems

hosted

Linux
Windows

All OS with a Java 7 VM

Docker
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

string, integer, double, boolean, date, object_id

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

by using the Octo plugin

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

RESTful HTTP/JSON API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

Java
JavaScript
Objective-C

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

yes

by Federation

Source-replica replication

yes

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

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

optimistic locking

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

User concepts

Access control

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

Access rights for users and roles

Users and groups based on OS-security mechanisms

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.