DBMS > Amazon DocumentDB vs. GeoMesa vs. HarperDB vs. NSDb

System Properties Comparison Amazon DocumentDB vs. GeoMesa vs. HarperDB vs. NSDb

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

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

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

Primary database model

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Website

aws.amazon.com/documentdb

www.geomesa.org

www.harperdb.io

nsdb.io

Technical documentation

aws.amazon.com/documentdb/resources

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

docs.harperdb.io/docs

nsdb.io/Architecture

Developer

CCRi and others

HarperDB

Initial release

2019

2014

2017

Current release

5.0.0, May 2024

3.1, August 2021

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

free community edition available

Open Source

Apache Version 2.0

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

Scala

Node.js

Java, Scala

Server operating systems

hosted

Linux
OS X

Linux
macOS

Data scheme

schema-free

yes

dynamic schema

Typing

predefined data types such as float or date

yes

JSON data types

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.

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL-like data manipulation statements

SQL-like query language

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

gRPC
HTTP REST
WebSocket

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Java
Scala

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

A table resides as a whole on one (or more) nodes in a cluster

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

depending on storage layer

yes

the nodes on which a table resides can be defined

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

Atomic single-document operations

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

yes

depending on the DBMS used for storage

Access rights for users and roles

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

A hybrid approach for homogeneous migration to an Amazon DocumentDB elastic cluster | Amazon Web Services
4 June 2024, AWS Blog

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

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

Use headless clusters in Amazon DocumentDB for cost-effective multi-Region resiliency | Amazon Web Services
8 March 2024, AWS Blog

Reduce cost and improve performance by migrating to Amazon DocumentDB 5.0 | Amazon Web Services
15 April 2024, AWS Blog

provided by Google News

Serent Capital invests in software firm HarperDB
12 June 2024, PE Hub

HarperDB Attracts Significant Growth Investment from Serent Capital
12 June 2024, Business Wire

HarperDB Receives Growth Investment from Serent Capital
12 June 2024, FinSMEs

Startups of the Year 2023: Meet HarperDB - A Database and Application Development Platform
22 June 2023, hackernoon.com

Jaxon Repp on HarperDB Distributed Database Platform
23 March 2022, InfoQ.com

provided by Google News

Share this page