DBMS > Brytlyt vs. Dolt vs. EJDB vs. SQLite

System Properties Comparison Brytlyt vs. Dolt vs. EJDB vs. SQLite

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

A MySQL compatible DBMS with Git-like versioning of data and schema

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

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

brytlyt.io

github.com/dolthub/dolt
www.dolthub.com

github.com/Softmotions/ejdb

www.sqlite.org

Technical documentation

docs.brytlyt.io

docs.dolthub.com

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

www.sqlite.org/docs.html

Developer

Brytlyt

DoltHub Inc

Softmotions

Dwayne Richard Hipp

Initial release

2016

2018

2012

2000

Current release

5.0, August 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPLv2

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.

Implementation language

C, C++ and CUDA

Server operating systems

Linux
OS X
Windows

Linux
macOS
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

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

CLI Client
HTTP REST

in-process shared library

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

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

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

yes

currently in alpha release

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

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

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

via file-system locks

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

Only one user is configurable, and must be specified in the config file at startup

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.