DBMS > FatDB vs. MarkLogic vs. MaxDB vs. SQLite vs. Yaacomo

System Properties Comparison FatDB vs. MarkLogic vs. MaxDB vs. SQLite vs. Yaacomo

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Operational and transactional Enterprise NoSQL database

A robust and reliable RDBMS optimized to run all major SAP solutions

Widely used embeddable, in-process RDBMS

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

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

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.marklogic.com

maxdb.sap.com

www.sqlite.org

yaacomo.com

Technical documentation

docs.marklogic.com

maxdb.sap.com/documentation

www.sqlite.org/docs.html

Developer

FatCloud

MarkLogic Corp.

SAP, acquired from Software AG (Adabas-D) in 1997

Dwayne Richard Hipp

Q2WEB GmbH

Initial release

2012

2001

1984

2000

2009

Current release

11.0, December 2022

7.9.10.12, February 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Limited community edition free

Open Source

Public Domain

commercial

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++

Server operating systems

Windows

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

server-less

Android
Linux
Windows

Data scheme

schema-free

Schema can be enforced

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Via inetgration in SQL Server

yes

SQL92

yes

SQL-92 is not fully supported

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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
JDBC
ODBC
WebDAV

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC

Supported programming languages

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

.Net
C#
Java
Perl
PHP
Python

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 applications

yes

via XQuery or JavaScript

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Source-replica replication

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

Eventual Consistency
Immediate Consistency

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

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

Can implement custom security layer via applications

Role-based access control at the document and subdocument levels

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.