DBMS > Brytlyt vs. EJDB vs. eXtremeDB vs. MySQL

System Properties Comparison Brytlyt vs. EJDB vs. eXtremeDB vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Natively in-memory DBMS with options for persistency, high-availability and clustering

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.27
Rank	#292	Overall
	#132	Relational DBMS

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	0.79
Rank	#212	Overall
	#100	Relational DBMS
	#18	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

brytlyt.io

github.com/Softmotions/ejdb

www.mcobject.com

www.mysql.com

Technical documentation

docs.brytlyt.io

github.com/Softmotions/ejdb/blob/master/README.md

www.mcobject.com/docs/extremedb.htm

dev.mysql.com/doc

Developer

Brytlyt

Softmotions

McObject

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2012

2001

1995

Current release

5.0, August 2023

8.2, 2021

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Implementation language

C, C++ and CUDA

C and C++

Server operating systems

Linux
OS X
Windows

server-less

AIX
HP-UX
Linux
macOS
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

support of XML interfaces available

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with the option: eXtremeSQL

yes

with proprietary extensions

APIs and other access methods

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

in-process shared library

.NET Client API
JDBC
JNI
ODBC
Proprietary protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
C
C#
C++
Java
Lua
Python
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

user defined functions

in PL/pgSQL

yes

proprietary syntax

Triggers

yes

by defining events

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

none

Active Replication Fabric™ for IoT
Multi-source replication

by means of eXtremeDB Cluster option
Source-replica replication

by means of eXtremeDB High Availability option

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

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Optimistic (MVCC) and pessimistic (locking) strategies available

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

User concepts

Access control

fine grained access rights according to SQL-standard

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.