DBMS > GeoMesa vs. Google Cloud Datastore vs. mSQL vs. OrigoDB vs. PostGIS

System Properties Comparison GeoMesa vs. Google Cloud Datastore vs. mSQL vs. OrigoDB vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

Spatial extension of PostgreSQL

Primary database model

Spatial DBMS

Document store

Relational DBMS

Document store
Object oriented DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.geomesa.org

cloud.google.com/datastore

hughestech.com.au/products/msql

origodb.com

postgis.net

Technical documentation

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

cloud.google.com/datastore/docs

origodb.com/docs

postgis.net/documentation

Developer

CCRi and others

Google

Hughes Technologies

Robert Friberg et al

Initial release

2014

2008

1994

2009

under the name LiveDB

2005

Current release

4.0.5, February 2024

4.4, October 2021

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free licenses can be provided

Open Source

GPL v2.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

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Server-side scripts

Stored procedures

using Google App Engine

yes

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication using Paxos

none

Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

none

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

depending on model

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

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

yes

depending on the DBMS used for storage

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Role based authorization

yes

based on PostgreSQL

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Higher Education PS rules out ghost students before PAC
29 November 2018, diggers.news

provided by Google News

Share this page