DBMS > Amazon Aurora vs. GeoMesa vs. ITTIA vs. Machbase Neo vs. MySQL

System Properties Comparison Amazon Aurora vs. GeoMesa vs. ITTIA vs. Machbase Neo vs. MySQL

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

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

Edge Time Series DBMS with Real-Time Stream Processing

TimeSeries DBMS for AIoT and BigData

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store

Relational DBMS

Document store
Spatial DBMS

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

Score	7.84
Rank	#44	Overall
	#28	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.36
Rank	#272	Overall
	#22	Time Series DBMS

Score	0.07
Rank	#348	Overall
	#34	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/rds/aurora

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

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

machbase.com/dbms

dev.mysql.com/doc

Developer

Amazon

CCRi and others

ITTIA L.L.C.

Machbase

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2015

2014

2007

2013

1995

Current release

5.0.1, July 2024

8.7

V8.0, August 2023

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

free test version 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.

Implementation language

Scala

C and C++

Server operating systems

hosted

Linux
Windows

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

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

yes

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC
RESTful HTTP API
WebSocket

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C
C++
JavaScript (Node.js)
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
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

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

depending on storage layer

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

yes

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

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

depending on storage layer

yes

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Database file passwords

simple password-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.