DBMS > GeoMesa vs. Ignite vs. InfinityDB vs. NSDb

System Properties Comparison GeoMesa vs. Ignite vs. InfinityDB vs. NSDb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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.

A Java embedded Key-Value Store which extends the Java Map interface

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Spatial DBMS

Key-value store
Relational DBMS

Key-value store

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

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

Score	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

apacheignite.readme.io/docs

boilerbay.com/infinitydb/manual

nsdb.io/Architecture

Developer

CCRi and others

Apache Software Foundation

Boiler Bay Inc.

Initial release

2014

2015

2002

2017

Current release

4.0.5, February 2024

Apache Ignite 2.6

4.0

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

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.

Implementation language

Scala

C++, Java, .Net

Java

Java, Scala

Server operating systems

Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
macOS

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

yes: int, bigint, decimal, string

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

manual creation possible, using inversions based on multi-value capability

all fields are automatically indexed

SQL

Support of SQL

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

SQL-like query language

APIs and other access methods

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

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

gRPC
HTTP REST
WebSocket

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Java

Java
Scala

Server-side scripts

Stored procedures

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

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

READ-COMMITTED or SERIALIZED

Eventual Consistency

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Security Hooks for custom implementations

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

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

Share this page