DBMS > Amazon SimpleDB vs. GeoMesa vs. Google BigQuery vs. MaxDB vs. SAP SQL Anywhere

System Properties Comparison Amazon SimpleDB vs. GeoMesa vs. Google BigQuery vs. MaxDB vs. SAP SQL Anywhere

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

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

Large scale data warehouse service with append-only tables

A robust and reliable RDBMS optimized to run all major SAP solutions

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Key-value store

Spatial DBMS

Relational DBMS

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

Score	1.88
Rank	#133	Overall
	#23	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

aws.amazon.com/simpledb

www.geomesa.org

cloud.google.com/bigquery

maxdb.sap.com

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.aws.amazon.com/simpledb

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

cloud.google.com/bigquery/docs

maxdb.sap.com/documentation

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Amazon

CCRi and others

Google

SAP, acquired from Software AG (Adabas-D) in 1997

SAP

formerly Sybase

Initial release

2007

2014

2010

1984

1992

Current release

5.0.0, May 2024

7.9.10.12, February 2024

17, July 2015

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Limited community edition free

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

C++

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

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.

yes

Secondary indexes

yes

All columns are indexed automatically

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
WebDAV

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C#
Java
Perl
PHP
Python

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Concurrent data updates can be detected by the application

Since BigQuery is designed for querying data

ACID

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

yes

User concepts

Access control

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

yes

depending on the DBMS used for storage

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.