DBMS > Amazon SimpleDB vs. Google Cloud Datastore vs. H2GIS vs. Hazelcast vs. MySQL

System Properties Comparison Amazon SimpleDB vs. Google Cloud Datastore vs. H2GIS vs. Hazelcast vs. MySQL

Editorial information provided by DB-Engines

Name

Description

Hosted simple database service by Amazon, with the data stored in the Amazon Cloud.

There is an unrelated product called SimpleDB developed by Edward Sciore

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

Spatial extension of H2

A widely adopted in-memory data grid

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Relational DBMS

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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

Score	1.85
Rank	#138	Overall
	#24	Key-value stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/simpledb

cloud.google.com/datastore

www.h2gis.org

hazelcast.com

www.mysql.com

Technical documentation

docs.aws.amazon.com/simpledb

cloud.google.com/datastore/docs

www.h2gis.org/docs/home

hazelcast.org/imdg/docs

dev.mysql.com/doc

Developer

Amazon

Google

CNRS

Hazelcast

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2007

2008

2013

2008

1995

Current release

5.3.6, November 2023

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

Open Source

Apache Version 2; commercial licenses available

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

Java

C and C++

Server operating systems

hosted

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

All columns are indexed automatically

yes

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

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

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Erlang
Java
PHP
Python
Ruby
Scala

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

Java

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

yes

based on H2

yes

Event Listeners, Executor Services

yes

proprietary syntax

Triggers

Callbacks using the Google Apps Engine

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

Sharding

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

based on H2

yes

Replicated Map

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

Eventual Consistency
Immediate Consistency

can be specified for read operations

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.

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

Concurrent data updates can be detected by the application

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

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.

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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

yes

based on H2

Role-based access control

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.