DBMS > AlaSQL vs. GeoMesa vs. Google Cloud Datastore vs. IBM Cloudant vs. MySQL

System Properties Comparison AlaSQL vs. GeoMesa vs. Google Cloud Datastore vs. IBM Cloudant vs. MySQL

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

Database as a Service offering based on Apache CouchDB

Widely used open source RDBMS

Primary database model

Document store
Relational DBMS

Spatial DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

alasql.org

www.geomesa.org

cloud.google.com/datastore

www.ibm.com/products/cloudant

www.mysql.com

Technical documentation

github.com/AlaSQL/alasql

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

cloud.google.com/datastore/docs

cloud.ibm.com/docs/Cloudant

dev.mysql.com/doc

Developer

Andrey Gershun & Mathias R. Wulff

CCRi and others

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2008

2010

1995

Current release

4.0.5, February 2024

8.4.0, April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache License 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

JavaScript

Scala

Erlang

C and C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

JavaScript API

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

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

JavaScript

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

using Google App Engine

View functions (Map-Reduce) in JavaScript

yes

proprietary syntax

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Multi-source replication using Paxos

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

atomic operations within a document possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

In-memory capabilities

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

yes

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)

Access rights for users can be defined per database

Users with fine-grained authorization concept

no user groups or roles

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.