DBMS > Amazon DocumentDB vs. Ignite vs. Infobright vs. SpatiaLite

System Properties Comparison Amazon DocumentDB vs. Ignite vs. Infobright vs. SpatiaLite

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.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Spatial extension of SQLite

Primary database model

Document store

Key-value store
Relational DBMS

Relational DBMS

Spatial DBMS

Secondary database models

Relational 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	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

aws.amazon.com/documentdb

ignite.apache.org

ignitetech.com/softwarelibrary/infobrightdb

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

aws.amazon.com/documentdb/resources

apacheignite.readme.io/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Apache Software Foundation

Ignite Technologies Inc.; formerly InfoBright Inc.

Alessandro Furieri

Initial release

2019

2015

2005

2008

Current release

Apache Ignite 2.6

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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.

Implementation language

C++, Java, .Net

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux
Windows

server-less

Data scheme

schema-free

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

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

yes

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

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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)

Source-replica replication

none

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

Transaction concepts

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

Atomic single-document operations

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

User concepts

Access control

Access rights for users and roles

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

AWS announces Amazon DocumentDB zero-ETL integration with Amazon OpenSearch Service
16 May 2024, AWS Blog

Use LangChain and vector search on Amazon DocumentDB to build a generative AI chatbot | Amazon Web Services
20 May 2024, AWS Blog

Vector search for Amazon DocumentDB (with MongoDB compatibility) is now generally available | Amazon Web Services
29 November 2023, AWS Blog

AWS announces Amazon DocumentDB I/O-Optimized
21 November 2023, AWS Blog

AWS announces vector search for Amazon DocumentDB
29 November 2023, AWS Blog

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

Apache Ignite: An Overview
6 September 2023, Open Source For You

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

Fire up big data processing with Apache Ignite
27 October 2016, InfoWorld

provided by Google News

Ignite Buys Database Vendor Infobright
2 May 2017, Datanami

provided by Google News

Share this page