DBMS > GeoMesa vs. Ignite vs. NSDb vs. Oracle Berkeley DB

System Properties Comparison GeoMesa vs. Ignite vs. NSDb vs. Oracle Berkeley DB

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.

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

Widely used in-process key-value store

Primary database model

Spatial DBMS

Key-value store
Relational DBMS

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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	#383	Overall
	#41	Time Series DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

www.geomesa.org

ignite.apache.org

nsdb.io

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

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

apacheignite.readme.io/docs

nsdb.io/Architecture

docs.oracle.com/cd/E17076_05/html/index.html

Developer

CCRi and others

Apache Software Foundation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2014

2015

2017

1994

Current release

4.0.5, February 2024

Apache Ignite 2.6

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

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.

Implementation language

Scala

C++, Java, .Net

Java, Scala

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Linux
OS X
Solaris
Windows

Linux
macOS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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

only with the Berkeley DB XML edition

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

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

SQL-like query language

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

gRPC
HTTP REST
WebSocket

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Java
Scala

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

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

Triggers

yes (cache interceptors and events)

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes (replicated cache)

Source-replica replication

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

Eventual Consistency

Foreign keys

Referential integrity

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

Using Apache Lucene

yes

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

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

Margo I. Seltzer | Berkman Klein Center
18 August 2020, Berkman Klein Center

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

How to store financial market data for backtesting
26 January 2019, Towards Data Science

The importance of bitcoin nodes and how to start one
9 May 2014, The Merkle News

provided by Google News

Share this page