DBMS > BaseX vs. Firebase Realtime Database vs. GeoMesa vs. Microsoft SQL Server

System Properties Comparison BaseX vs. Firebase Realtime Database vs. GeoMesa vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.56
Rank	#141	Overall
	#4	Native XML DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Website

basex.org

firebase.google.com/products/realtime-database

www.geomesa.org

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

Technical documentation

docs.basex.org

firebase.google.com/docs/database

www.geomesa.org/documentation/stable/user/index.html

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

Developer

BaseX GmbH

Google

acquired by Google 2014

CCRi and others

Microsoft

Initial release

2007

2012

2014

1989

Current release

11.2, August 2024

5.0.1, July 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

BSD license

commercial

Open Source

Apache License 2.0

commercial

restricted free version is available

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

Java

Scala

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

XQuery supports types

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

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

Android
iOS
JavaScript API
RESTful HTTP API

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

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

Java
JavaScript
Objective-C

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

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

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

Triggers

yes

via events

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

multiple readers, single writer

yes

ACID

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.

depending on storage layer

yes

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

yes, based on authentication and database rules

yes

depending on the DBMS used for storage

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.