DBMS > Firebase Realtime Database vs. MarkLogic vs. searchxml vs. SQLite

System Properties Comparison Firebase Realtime Database vs. MarkLogic vs. searchxml 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.

Operational and transactional Enterprise NoSQL database

DBMS for structured and unstructured content wrapped with an application server

Widely used embeddable, in-process RDBMS

Primary database model

Document store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Native XML DBMS
Search engine

Relational DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.marklogic.com

www.searchxml.net/category/products

www.sqlite.org

Technical documentation

firebase.google.com/docs/database

docs.marklogic.com

www.searchxml.net/support/handouts

www.sqlite.org/docs.html

Developer

Google

acquired by Google 2014

MarkLogic Corp.

informationpartners gmbh

Dwayne Richard Hipp

Initial release

2012

2001

2015

2000

Current release

11.0, December 2022

1.0

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

restricted free version is available

commercial

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

Linux
OS X
Windows

Windows

server-less

Data scheme

schema-free

Schema can be enforced

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL92

yes

SQL-92 is not fully supported

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
JavaScript
Objective-C

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

C++

most other programming languages supported via APIs

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'

yes

via XQuery or JavaScript

yes

on the application server

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

sychronisation to multiple collections

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

can act as a resource manager in an XA/JTA transaction

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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, with Range Indexes

yes

User concepts

Access control

yes, based on authentication and database rules

Role-based access control at the document and subdocument levels

Domain, group and role-based access control at the document level and for application services

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.