DBMS > GeoMesa vs. Microsoft Azure Table Storage

System Properties Comparison GeoMesa vs. Microsoft Azure Table Storage

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and Microsoft Azure Table Storage with MongoDB, Elasticsearch and PostgreSQL.

Editorial information provided by DB-Engines

Name

Description

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

A Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Spatial DBMS

Wide column store

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	4.92
Rank	#73	Overall
	#6	Wide column stores

Website

www.geomesa.org

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

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

Developer

CCRi and others

Microsoft

Initial release

2014

2012

Current release

4.0.5, February 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

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 API

Supported programming languages

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

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 based on private key authentication or shared access signatures

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

Azure Cosmos DB Data Migration tool imports from Azure Table storage | Azure updates
5 May 2015, Microsoft

How to use Azure Table storage in .Net
14 January 2019, InfoWorld

How to Use C# Azure.Data.Tables SDK with Azure Cosmos DB
9 July 2021, hackernoon.com

How to write data to Azure Table Store with an Azure Function
14 April 2017, Experts Exchange

Testing Precompiled Azure Functions Locally with Storage Emulator
8 March 2018, Visual Studio Magazine

provided by Google News

Share this page