DBMS > Adabas vs. MarkLogic vs. OrigoDB vs. Realm vs. RocksDB

System Properties Comparison Adabas vs. MarkLogic vs. OrigoDB vs. Realm vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

Operational and transactional Enterprise NoSQL database

A fully ACID in-memory object graph database

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Primary database model

Multivalue DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store
Object oriented DBMS

Document store

Key-value store

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.softwareag.com/en_corporate/platform/adabas-natural.html

Technical documentation

docs.marklogic.com

origodb.com/docs

realm.io/docs

github.com/facebook/rocksdb/wiki

Developer

Software AG

MarkLogic Corp.

Robert Friberg et al

Realm, acquired by MongoDB in May 2019

Facebook, Inc.

Initial release

1971

2001

2009

under the name LiveDB

2014

2013

Current release

11.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

BSD

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

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Windows

Linux
Windows

Android
Backend: server-less
iOS
Windows

Linux

Data scheme

yes

schema-free

Schema can be enforced

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

SQL92

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

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

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

Natural

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

.Net

.Net
Java

with Android only
Objective-C
React Native
Swift

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

in Natural

yes

via XQuery or JavaScript

yes

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Domain Events

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

Source-replica replication

none

yes

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

depending on model

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

In-Memory realm

yes

User concepts

Access control

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

Role-based access control at the document and subdocument levels

Role based authorization

yes

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.