DBMS > BaseX vs. MarkLogic vs. SQLite vs. ToroDB

System Properties Comparison BaseX vs. MarkLogic vs. SQLite vs. ToroDB

Please select another system to include it in the comparison.

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.

Operational and transactional Enterprise NoSQL database

Widely used embeddable, in-process RDBMS

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

Primary database model

Native XML DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Document store

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

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

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

basex.org

www.progress.com/marklogic

www.sqlite.org

github.com/torodb/server

Technical documentation

docs.basex.org

www.progress.com/marklogic/documentation

www.sqlite.org/docs.html

Developer

BaseX GmbH

MarkLogic Corp.

Dwayne Richard Hipp

8Kdata

Initial release

2007

2001

2000

2016

Current release

11.0, June 2024

11.0, December 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

BSD license

commercial

restricted free version is available

Open Source

Public Domain

Open Source

AGPL-V3

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

C++

Java

Server operating systems

Linux
OS X
Windows

server-less

All OS with a Java 7 VM

Data scheme

schema-free

Schema can be enforced

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

XQuery supports types

yes

not rigid because of 'dynamic typing' concept.

yes

string, integer, double, boolean, date, object_id

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

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

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

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

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

via XQuery or JavaScript

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

Source-replica replication

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

Immediate Consistency

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

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

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.

yes, with Range Indexes

yes

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

Role-based access control at the document and subdocument levels

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.