DBMS > Amazon DocumentDB vs. Brytlyt vs. MySQL vs. Spark SQL vs. Trafodion

System Properties Comparison Amazon DocumentDB vs. Brytlyt vs. MySQL vs. Spark SQL vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

Widely used open source RDBMS

Spark SQL is a component on top of 'Spark Core' for structured data processing

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.89
Rank	#137	Overall
	#24	Document stores

Score	0.38
Rank	#279	Overall
	#126	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	19.15
Rank	#33	Overall
	#20	Relational DBMS

Website

aws.amazon.com/documentdb

Technical documentation

aws.amazon.com/documentdb/resources

docs.brytlyt.io

dev.mysql.com/doc

spark.apache.org/docs/latest/sql-programming-guide.html

trafodion.apache.org/documentation.html

Developer

Brytlyt

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Apache Software Foundation, originally developed by HP

Initial release

2019

2016

1995

2014

Current release

5.0, August 2023

8.3.0, January 2024

3.5.0 ( 2.13), September 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

Open Source

Apache 2.0

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 CUDA

C and C++

Scala

C++, Java

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux

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

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like DML and DDL statements

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

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

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

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

Java
Python
R
Scala

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

proprietary syntax

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes, utilizing Spark Core

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Source-replica replication

Multi-source replication
Source-replica replication

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic single-document operations

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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.

yes

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.