DBMS > BaseX vs. Faircom DB vs. SpatiaLite vs. ToroDB vs. XTDB

System Properties Comparison BaseX vs. Faircom DB vs. SpatiaLite vs. ToroDB vs. XTDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Spatial extension of SQLite

A MongoDB-compatible JSON document store, built on top of PostgreSQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Native XML DBMS

Key-value store
Relational DBMS

Spatial DBMS

Document store

Secondary database models

Relational DBMS

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

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

basex.org

www.faircom.com/products/faircom-db

www.gaia-gis.it/fossil/libspatialite/index

github.com/torodb/server

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.basex.org

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.gaia-gis.it/gaia-sins/spatialite_topics.html

www.xtdb.com/docs

Developer

BaseX GmbH

FairCom Corporation

Alessandro Furieri

8Kdata

Juxt Ltd.

Initial release

2007

1979

2008

2016

2019

Current release

10.7, August 2023

V12, November 2020

5.0.0, August 2020

1.19, September 2021

License

Commercial or Open Source

Open Source

BSD license

commercial

Restricted, free version available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

AGPL-V3

Open Source

MIT License

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

ANSI C, C++

C++

Java

Clojure

Server operating systems

Linux
OS X
Windows

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

server-less

All OS with a Java 7 VM

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

schema free, schema optional, schema required, partial schema,

yes

schema-free

Typing

predefined data types such as float or date

XQuery supports types

yes, ANSI SQL Types, JSON, typed binary structures

yes

string, integer, double, boolean, date, object_id

yes, extensible-data-notation format

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.

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

HTTP REST
JDBC

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

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

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

Clojure
Java

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

none

Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

multiple readers, single writer

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Fine grained access rights according to SQL-standard with additional protections for files

Access rights for users and roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

XML Injection Attacks: What to Know About XPath, XQuery, XXE & More
18 May 2022, Hashed Out by The SSL Store™

9 Skills You Need to Become a Data Engineer
2 November 2022, KDnuggets

provided by Google News

FairCom kicks off new era of database technology USA - English
10 November 2020, PR Newswire

provided by Google News

Share this page