DBMS > Brytlyt vs. EJDB vs. jBASE vs. Vitess

System Properties Comparison Brytlyt vs. EJDB vs. jBASE vs. Vitess

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)

A robust multi-value DBMS comprising development tools and middleware

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

brytlyt.io

github.com/Softmotions/ejdb

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

vitess.io

Technical documentation

docs.brytlyt.io

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

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

vitess.io/docs

Developer

Brytlyt

Softmotions

Rocket Software (formerly Zumasys)

The Linux Foundation, PlanetScale

Initial release

2016

2012

1991

2013

Current release

5.0, August 2023

5.7

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

Open Source

Apache Version 2.0, commercial licenses 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

Server operating systems

Linux
OS X
Windows

server-less

AIX
Linux
Windows

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

optional

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

Embedded SQL for jBASE in BASIC

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
JDBC
MySQL protocol
ODBC

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
Basic
Jabbascript
Java

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

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

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

Eventual Consistency across shards
Immediate Consistency within a shard

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

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

Access rights can be defined down to the item level

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Opensignal Announces Acquisition of Brytlyt GPU-based Data Analytics & Visualization Technology
5 June 2024, PR Web

Brytlyt releases version 5.0, introducing a more intuitive, intelligent and flexible analytics platform
1 August 2023, PR Newswire

London data analytics startup Brytlyt raises €4.43M from Amsterdam-based Finch Capital, others
22 December 2021, Silicon Canals

London’s Brytlyt raises €4.4 million for its data analytics and visualisation technology
22 December 2021, EU-Startups

Brytlyt raises £3.8m for '1000x faster analytics'
22 December 2021, BusinessCloud

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

PlanetScale offers undo button to reverse schema migration without losing data
24 March 2022, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page