DBMS > Ignite vs. MySQL vs. ObjectBox vs. RavenDB

System Properties Comparison Ignite vs. MySQL vs. ObjectBox vs. RavenDB

Please select another system to include it in the comparison.

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.

Widely used open source RDBMS

Extremely fast embedded database for small devices, IoT and Mobile

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Object oriented DBMS

Document store

Secondary database models

Document store
Spatial DBMS

Time Series DBMS

Graph DBMS
Spatial DBMS
Time Series 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	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

Technical documentation

apacheignite.readme.io/docs

dev.mysql.com/doc

docs.objectbox.io

ravendb.net/docs

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

ObjectBox Limited

Hibernating Rhinos

Initial release

2015

1995

2017

2010

Current release

Apache Ignite 2.6

8.4.0, April 2024

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache License 2.0

Open Source

AGPL version 3, commercial license available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++, Java, .Net

C and C++

Server operating systems

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Android
iOS
Linux
macOS
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

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

yes

with proprietary extensions

SQL-like query language (RQL)

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary native API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

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

yes

proprietary syntax

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication
Source-replica replication

online/offline synchronization between client and server

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

not for MyISAM storage engine

ACID

ACID, Cluster-wide transaction available

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

User concepts

Access control

Security Hooks for custom implementations

Users with fine-grained authorization concept

no user groups or roles

yes

Authorization levels configured per client per database

More information provided by the system vendor

News

Evolution of search: traditional vs vector search
23 May 2024

On-device Vector Database for Dart/Flutter
21 May 2024

The first On-Device Vector Database: ObjectBox 4.0
16 May 2024

SQLite and SQLite alternatives – a comprehensive overview
7 May 2024

Edge AI: The era of on-device AI
23 April 2024

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.