DBMS > Amazon DocumentDB vs. Ignite vs. MySQL vs. searchxml

System Properties Comparison Amazon DocumentDB vs. Ignite vs. MySQL vs. searchxml

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Native XML DBMS
Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

aws.amazon.com/documentdb

ignite.apache.org

www.mysql.com

www.searchxml.net/category/products

Technical documentation

aws.amazon.com/documentdb/resources

apacheignite.readme.io/docs

dev.mysql.com/doc

www.searchxml.net/support/handouts

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

informationpartners gmbh

Initial release

2019

2015

1995

2015

Current release

Apache Ignite 2.6

8.4.0, April 2024

1.0

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Cloud-based only

Only available as a cloud service

yes

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

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Windows

Data scheme

schema-free

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

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

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

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

most other programming languages supported via APIs

Server-side scripts

Stored procedures

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

yes

proprietary syntax

yes

on the application server

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes (replicated cache)

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic single-document operations

ACID

not for MyISAM storage engine

multiple readers, single writer

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

Access rights for users and roles

Security Hooks for custom implementations

Users with fine-grained authorization concept

no user groups or roles

Domain, group and role-based access control at the document level and for application services

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.