DBMS > MarkLogic vs. RocksDB vs. SAP Advantage Database Server vs. SiteWhere vs. SpatiaLite

System Properties Comparison MarkLogic vs. RocksDB vs. SAP Advantage Database Server vs. SiteWhere vs. SpatiaLite

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Operational and transactional Enterprise NoSQL database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Low-cost RDBMS with access to ISAM and FoxPro data structures

M2M integration platform for persisting/querying time series data

Spatial extension of SQLite

Primary database model

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Secondary database models

Relational DBMS

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

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

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

www.progress.com/marklogic

rocksdb.org

www.sap.com/products/advantage-database-server.html

github.com/sitewhere/sitewhere

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

Technical documentation

www.progress.com/marklogic/documentation

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

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

Developer

MarkLogic Corp.

Facebook, Inc.

Sybase, SAP

SiteWhere

Alessandro Furieri

Initial release

2001

2013

1993

2010

2008

Current release

11.0, December 2022

9.2.1, May 2024

5.0.0, August 2020

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

BSD

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

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

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

C++

Java

C++

Server operating systems

Linux
OS X
Windows

Linux

Linux
Windows

Linux
OS X
Windows

server-less

Data scheme

schema-free

Schema can be enforced

schema-free

yes

predefined scheme

yes

Typing

predefined data types such as float or date

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

SQL92

yes

APIs and other access methods

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

C++ API
Java API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

HTTP REST

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

selectable replication factor

based on HBase

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

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.

yes, with Range Indexes

yes

caching of (temporary) tables can be configured

yes

User concepts

Access control

Role-based access control at the document and subdocument levels

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.