DBMS > Brytlyt vs. Databend vs. EJDB vs. Microsoft Azure Cosmos DB

System Properties Comparison Brytlyt vs. Databend vs. EJDB vs. Microsoft Azure Cosmos DB

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

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

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.34
Rank	#283	Overall
	#130	Relational DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

brytlyt.io

github.com/datafuselabs/databend
www.databend.com

github.com/Softmotions/ejdb

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.brytlyt.io

docs.databend.com

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

learn.microsoft.com/azure/cosmos-db

Developer

Brytlyt

Databend Labs

Softmotions

Microsoft

Initial release

2016

2021

2012

2014

Current release

5.0, August 2023

1.0.59, April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPLv2

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++ and CUDA

Rust

Server operating systems

Linux
OS X
Windows

hosted
Linux
macOS

server-less

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

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

CLI Client
JDBC
RESTful HTTP API

in-process shared library

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

Go
Java
JavaScript (Node.js)
Python
Rust

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

yes

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles

Access rights can be defined down to the item level

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.