DBMS > GeoMesa vs. IBM Cloudant

System Properties Comparison GeoMesa vs. IBM Cloudant

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and IBM Cloudant with MongoDB and Elasticsearch.

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering based on Apache CouchDB

Primary database model

Spatial DBMS

Document store

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

Score	0.74
Rank	#215	Overall
	#4	Spatial DBMS

Score	2.53
Rank	#103	Overall
	#19	Document stores

Website

www.geomesa.org

www.ibm.com/products/cloudant

Technical documentation

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

cloud.ibm.com/docs/Cloudant

Developer

CCRi and others

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2014

2010

Current release

5.0.1, July 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

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

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

SQL

Support of SQL

APIs and other access methods

RESTful HTTP/JSON API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

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

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

Durability

Support for making data persistent

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

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.com

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

Seamless integration of data from unconventional source systems into Business Intelligence using data science techniques
24 October 2023, Data Science Central

Truck Tracker: An IoT Pattern Using IBM Cloud Services
6 January 2022, ibm.com

IBM’s new CEO lays out his roadmap
6 May 2020, TechCentral.ie

provided by Google News

Share this page