DBMS > Dolt vs. Ignite vs. Machbase Neo vs. SAP HANA

System Properties Comparison Dolt vs. Ignite vs. Machbase Neo vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

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

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

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

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

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

ignite.apache.org

machbase.com

www.sap.com/products/hana.html

Technical documentation

docs.dolthub.com

apacheignite.readme.io/docs

machbase.com/dbms

help.sap.com/hana

Developer

DoltHub Inc

Apache Software Foundation

Machbase

SAP

Initial release

2018

2015

2013

2010

Current release

Apache Ignite 2.6

V8.0, August 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

free test version 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

Server operating systems

Linux
macOS
Windows

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Appliance or cloud-service

Data scheme

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

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

SQL-like query language

yes

APIs and other access methods

CLI Client
HTTP REST

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

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

JDBC
ODBC

Supported programming languages

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

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

yes

currently in alpha release

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

SQLScript, R

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

yes (replicated cache)

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

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

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

Security Hooks for custom implementations

simple password-based access control

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.