DBMS > GeoMesa vs. IBM Cloudant vs. JSqlDb vs. Riak KV

System Properties Comparison GeoMesa vs. IBM Cloudant 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

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

Database as a Service offering based on Apache CouchDB

JavaScript Query Language Database, stores JavaScript objects and primitives

Distributed, fault tolerant key-value store

Primary database model

Spatial DBMS

Document store

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	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

www.geomesa.org

www.ibm.com/products/cloudant

jsqldb.org (offline)

Technical documentation

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

cloud.ibm.com/docs/Cloudant

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

Developer

CCRi and others

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Konrad von Backstrom

OpenSource, formerly Basho Technologies

Initial release

2014

2010

2018

2009

Current release

4.0.5, February 2024

0.8, December 2018

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

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

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

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

View functions (Map-Reduce) in JavaScript

functions in JavaScript

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

none

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

yes

depending on the DBMS used for storage

Access rights for users can be defined per database

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

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, IBM

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, IBM

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

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

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

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

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page