DBMS > Amazon Aurora vs. Brytlyt vs. Google BigQuery vs. Machbase Neo vs. MySQL

System Properties Comparison Amazon Aurora vs. Brytlyt vs. Google BigQuery vs. Machbase Neo vs. MySQL

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Large scale data warehouse service with append-only tables

TimeSeries DBMS for AIoT and BigData

Widely used open source RDBMS

Primary database model

Relational DBMS

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.84
Rank	#44	Overall
	#28	Relational DBMS

Score	0.27
Rank	#292	Overall
	#132	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational 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

brytlyt.io

cloud.google.com/bigquery

machbase.com

www.mysql.com

Technical documentation

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

docs.brytlyt.io

cloud.google.com/bigquery/docs

machbase.com/dbms

dev.mysql.com/doc

Developer

Amazon

Brytlyt

Google

Machbase

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2015

2016

2010

2013

1995

Current release

5.0, August 2023

V8.0, August 2023

9.0.0, July 2024

License

Commercial or Open Source

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

C, C++ and CUDA

C and C++

Server operating systems

hosted

Linux
OS X
Windows

hosted

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

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

specific XML-type available, but no XML query functionality.

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

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

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

in PL/pgSQL

user defined functions

in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Since BigQuery is designed for querying data

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

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

Google Cloud Identity & Access Management (IAM)

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.