DBMS > Ignite vs. Machbase Neo vs. MarkLogic vs. SAP HANA vs. Valentina Server

System Properties Comparison Ignite vs. Machbase Neo vs. MarkLogic vs. SAP HANA vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

TimeSeries DBMS for AIoT and BigData

Operational and transactional Enterprise NoSQL database

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

Object-relational database and reports server

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

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

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

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

ignite.apache.org

machbase.com

www.marklogic.com

www.sap.com/products/hana.html

www.valentina-db.net

Technical documentation

apacheignite.readme.io/docs

machbase.com/dbms

docs.marklogic.com

help.sap.com/hana

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Apache Software Foundation

Machbase

MarkLogic Corp.

SAP

Paradigma Software

Initial release

2015

2013

2001

2010

1999

Current release

Apache Ignite 2.6

V8.0, August 2023

11.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

5.7.5

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free test version available

commercial

restricted free version is 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++, Java, .Net

C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux
OS X
Windows

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

yes

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

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

yes

SQL92

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

via XQuery or JavaScript

SQLScript, R

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

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

volatile and lookup table

yes, with Range Indexes

yes

User concepts

Access control

Security Hooks for custom implementations

simple password-based access control

Role-based access control at the document and subdocument levels

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.