DBMS > AgensGraph vs. Brytlyt vs. Graph Engine vs. Microsoft Azure Cosmos DB

System Properties Comparison AgensGraph vs. Brytlyt vs. Graph Engine vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Graph DBMS
Key-value 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.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

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

Website

bitnine.net/agensgraph

brytlyt.io

www.graphengine.io

azure.microsoft.com/services/cosmos-db

Technical documentation

bitnine.net/documentation

docs.brytlyt.io

www.graphengine.io/docs/manual

learn.microsoft.com/azure/cosmos-db

Developer

Bitnine Global Inc.

Brytlyt

Microsoft

Initial release

2016

2010

2014

Current release

2.1, December 2018

5.0, August 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

MIT License

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

.NET and C

Server operating systems

Linux
OS X
Windows

.NET

hosted

Data scheme

depending on used data model

yes

schema-free

Typing

predefined data types such as float or date

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

Cypher Query Language
JDBC

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

RESTful HTTP API

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

Supported programming languages

C
Java
JavaScript
Python

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C#
C++
F#
Visual Basic

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

Server-side scripts

Stored procedures

yes

user defined functions

in PL/pgSQL

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

horizontal partitioning

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.