DBMS > Amazon Aurora vs. Databricks vs. gStore vs. Machbase Neo vs. MySQL

System Properties Comparison Amazon Aurora vs. Databricks vs. gStore vs. Machbase Neo vs. MySQL

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

A native Graph DBMS to store and maintain very large RDF datasets.

TimeSeries DBMS for AIoT and BigData

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store
Relational DBMS

Graph DBMS
RDF store

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	81.08
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	0.14
Rank	#342	Overall
	#34	Graph DBMS
	#16	RDF stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/rds/aurora

Technical documentation

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

docs.databricks.com

en.gstore.cn/#/enDocs

machbase.com/dbms

dev.mysql.com/doc

Developer

Amazon

Databricks

Machbase

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2015

2013

2016

2013

1995

Current release

1.2, November 2023

V8.0, August 2023

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

BSD

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.

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

Implementation language

C++

C and C++

Server operating systems

hosted

Linux

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

schema-free and OWL/RDFS-schema support

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

SQL

Support of SQL

yes

with Databricks SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

HTTP API
SPARQL 1.1

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

Python
R
Scala

C++
Java
JavaScript (Node.js)
PHP
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

user defined functions and aggregates

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users, roles and permissions, Role-Based Access Control (RBAC) supported

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.