DBMS > MarkLogic vs. Memcached vs. SAP HANA vs. Transbase

System Properties Comparison MarkLogic vs. Memcached vs. SAP HANA vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Operational and transactional Enterprise NoSQL database

In-memory key-value store, originally intended for caching

In-memory, column based data store. Available as appliance or cloud service

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial 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	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

www.progress.com/marklogic

www.memcached.org

www.sap.com/products/hana.html

www.transaction.de/en/products/transbase.html

Technical documentation

www.progress.com/marklogic/documentation

github.com/memcached/memcached/wiki

help.sap.com/hana

www.transaction.de/en/products/transbase/features.html

Developer

MarkLogic Corp.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SAP

Transaction Software GmbH

Initial release

2001

2003

2010

1987

Current release

11.0, December 2022

1.6.27, May 2024

2.0 SPS07 (April 4, 2023), April 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

BSD license

commercial

free development license

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

C and C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Unix
Windows

Appliance or cloud-service

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

Schema can be enforced

schema-free

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

Proprietary protocol

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Repcached, a Memcached patch, provides this functionallity

yes

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

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

yes

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

User concepts

Access control

Role-based access control at the document and subdocument levels

yes

using SASL (Simple Authentication and Security Layer) protocol

yes

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.