DBMS > FileMaker vs. Firebase Realtime Database vs. MarkLogic vs. Microsoft Azure Data Explorer vs. SQLite

System Properties Comparison FileMaker vs. Firebase Realtime Database vs. MarkLogic vs. Microsoft Azure Data Explorer vs. SQLite

Editorial information provided by DB-Engines

Name

Description

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

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

Fully managed big data interactive analytics platform

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Document store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

column oriented

Relational DBMS

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	47.91
Rank	#20	Overall
	#14	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.claris.com/filemaker

firebase.google.com/products/realtime-database

www.marklogic.com

azure.microsoft.com/services/data-explorer

www.sqlite.org

Technical documentation

www.claris.com/resources/documentation

firebase.google.com/docs/database

docs.marklogic.com

docs.microsoft.com/en-us/azure/data-explorer

www.sqlite.org/docs.html

Developer

Claris

a subsidiary of Apple

Google

acquired by Google 2014

MarkLogic Corp.

Microsoft

Dwayne Richard Hipp

Initial release

1983

2012

2001

2019

2000

Current release

19.4.1, November 2021

11.0, December 2022

cloud service with continuous releases

3.46.0 (23 May 2024), May 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

iOS

client part only
Linux
OS X
Windows

hosted

Linux
OS X
Windows

hosted

server-less

Data scheme

yes

schema-free

Schema can be enforced

Fixed schema with schema-less datatypes (dynamic)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

A http query request can return the data in XML format

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

via plugins

yes

SQL92

Kusto Query Language (KQL), SQL subset

yes

SQL-92 is not fully supported

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

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

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

PHP

Java
JavaScript
Objective-C

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

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

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

yes

limited functionality with using 'rules'

yes

via XQuery or JavaScript

Yes, possible languages: KQL, Python, R

Triggers

yes

Callbacks are triggered when data changes

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Spark connector (open source): github.com/Azure/azure-kusto-spark

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

Eventual Consistency
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

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

simple rights management via user accounts and connection to external directory services

yes, based on authentication and database rules

Role-based access control at the document and subdocument levels

Azure Active Directory Authentication

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.