DBMS > Brytlyt vs. HarperDB vs. MySQL vs. Realm vs. SQLite

System Properties Comparison Brytlyt vs. HarperDB vs. MySQL vs. Realm vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Widely used open source RDBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

docs.brytlyt.io

docs.harperdb.io/docs

dev.mysql.com/doc

realm.io/docs

www.sqlite.org/docs.html

Developer

Brytlyt

HarperDB

Oracle

since 2010, originally MySQL AB, then Sun

Realm, acquired by MongoDB in May 2019

Dwayne Richard Hipp

Initial release

2016

2017

1995

2014

2000

Current release

5.0, August 2023

3.1, August 2021

8.4.0, April 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Public Domain

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

Node.js

C and C++

Server operating systems

Linux
OS X
Windows

Linux
OS X

FreeBSD
Linux
OS X
Solaris
Windows

Android
Backend: server-less
iOS
Windows

server-less

Data scheme

yes

dynamic schema

yes

dynamic column types

Typing

predefined data types such as float or date

yes

JSON data types

yes

not rigid because of 'dynamic typing' concept.

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 data manipulation statements

yes

with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

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

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

.Net
Java

with Android only
Objective-C
React Native
Swift

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

Custom Functions

since release 3.1

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

A table resides as a whole on one (or more) nodes in a cluster

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

the nodes on which a table resides can be defined

Multi-source replication
Source-replica replication

none

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

yes

Transaction concepts

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

ACID

Atomic execution of specific 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

via file-system locks

Durability

Support for making data persistent

yes

yes, using LMDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-Memory realm

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

yes

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.