DBMS > Brytlyt vs. MySQL vs. RavenDB vs. Trafodion vs. Valentina Server

System Properties Comparison Brytlyt vs. MySQL vs. RavenDB vs. Trafodion vs. Valentina Server

Editorial information provided by DB-Engines

Name

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

Description

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

Widely used open source RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

Transactional SQL-on-Hadoop DBMS

Object-relational database and reports server

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

Technical documentation

docs.brytlyt.io

dev.mysql.com/doc

ravendb.net/docs

trafodion.apache.org/documentation.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Brytlyt

Oracle

since 2010, originally MySQL AB, then Sun

Hibernating Rhinos

Apache Software Foundation, originally developed by HP

Paradigma Software

Initial release

2016

1995

2010

2014

1999

Current release

5.0, August 2023

8.4.0, April 2024

5.4, July 2022

2.3.0, February 2019

5.7.5

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL version 3, commercial license available

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

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++

C++, Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

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 query language (RQL)

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET
JDBC
ODBC

ODBC

Supported programming languages

.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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

proprietary syntax

yes

Java Stored Procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID, Cluster-wide transaction available

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Authorization levels configured per client per database

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.