DBMS > Firebase Realtime Database vs. Manticore Search vs. Microsoft SQL Server vs. SQLite

System Properties Comparison Firebase Realtime Database vs. Manticore Search vs. Microsoft SQL Server vs. SQLite

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.

Multi-storage database for search, including full-text search.

Microsofts flagship relational DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS
Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

firebase.google.com/products/realtime-database

manticoresearch.com

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

www.sqlite.org

Technical documentation

firebase.google.com/docs/database

manual.manticoresearch.com

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

www.sqlite.org/docs.html

Developer

Google

acquired by Google 2014

Manticore Software

Microsoft

Dwayne Richard Hipp

Initial release

2012

2017

1989

2000

Current release

6.0, February 2023

SQL Server 2022, November 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

restricted free version is available

Open Source

Public Domain

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

FreeBSD
Linux
macOS
Windows

Linux
Windows

server-less

Data scheme

schema-free

Fixed schema

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes

not rigid because of 'dynamic typing' concept.

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 index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
JavaScript
Objective-C

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

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

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

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

Sharding

Partitioning is done manually, search queries against distributed index is supported

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

yes, but depending on the SQL-Server Edition

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

yes

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

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

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.