DBMS > MarkLogic vs. SAP HANA vs. Vitess vs. Yaacomo

System Properties Comparison MarkLogic vs. SAP HANA vs. Vitess vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Operational and transactional Enterprise NoSQL database

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

Scalable, distributed, cloud-native DBMS, extending MySQL

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

Primary database model

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
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	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

www.marklogic.com

www.sap.com/products/hana.html

vitess.io

yaacomo.com

Technical documentation

docs.marklogic.com

help.sap.com/hana

vitess.io/docs

Developer

MarkLogic Corp.

SAP

The Linux Foundation, PlanetScale

Q2WEB GmbH

Initial release

2001

2010

2013

2009

Current release

11.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

15.0.2, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

Apache Version 2.0, commercial licenses available

commercial

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

Server operating systems

Linux
OS X
Windows

Appliance or cloud-service

Docker
Linux
macOS

Android
Linux
Windows

Data scheme

schema-free

Schema can be enforced

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

with proprietary extensions

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

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

SQLScript, R

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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 across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.