DBMS > Amazon DocumentDB vs. GeoMesa vs. JSqlDb vs. Riak KV

System Properties Comparison Amazon DocumentDB vs. GeoMesa vs. JSqlDb vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

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.

JavaScript Query Language Database, stores JavaScript objects and primitives

Distributed, fault tolerant key-value store

Primary database model

Document store

Spatial DBMS

Document store
Object oriented DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

aws.amazon.com/documentdb

www.geomesa.org

jsqldb.org (offline)

Technical documentation

aws.amazon.com/documentdb/resources

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

www.tiot.jp/riak-docs/riak/kv/latest

Developer

CCRi and others

Konrad von Backstrom

OpenSource, formerly Basho Technologies

Initial release

2019

2014

2018

2009

Current release

4.0.5, February 2024

0.8, December 2018

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

hosted

Linux
macOS
Windows

Linux
OS X

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.

Secondary indexes

yes

restricted

SQL

Support of SQL

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

HTTP API
Native Erlang Interface

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

JavaScript

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

functions in JavaScript

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

Sharding

no "single point of failure"

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

none

selectable replication factor

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

Eventual Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

links between data sets can be stored

Transaction concepts

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

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

yes

In-memory capabilities

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

depending on storage layer

User concepts

Access control

Access rights for users and roles

yes

depending on the DBMS used for storage

yes, using Riak Security

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

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

AWS announces vector search for Amazon DocumentDB
29 November 2023, 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

Game Developer's Guide to Amazon DocumentDB (with MongoDB compatibility) Part Three: Operation Best Practices ...
25 January 2024, AWS Blog

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Basho distributes Riak to more customers - DCD
28 November 2013, DatacenterDynamics

provided by Google News

Share this page