DBMS > Firebase Realtime Database vs. Linter vs. Microsoft SQL Server vs. TerminusDB

System Properties Comparison Firebase Realtime Database vs. Linter vs. Microsoft SQL Server vs. TerminusDB

Please select another system to include it in the comparison.

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.

RDBMS for high security requirements

Microsofts flagship relational DBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store

Relational DBMS

Graph DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

firebase.google.com/products/realtime-database

linter.ru

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

terminusdb.com

Technical documentation

firebase.google.com/docs/database

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

terminusdb.github.io/terminusdb/#

Developer

Google

acquired by Google 2014

relex.ru

Microsoft

DataChemist Ltd.

Initial release

2012

1990

1989

2018

Current release

SQL Server 2022, November 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL V3

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

C++

Prolog, Rust

Server operating systems

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
Windows

Linux

Data scheme

schema-free

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

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

JavaScript
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

proprietary syntax with the possibility to convert from PL/SQL

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

yes

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

Journaling Streams

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

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 journaling

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

Role-based access control

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.