DBMS > Brytlyt vs. LevelDB vs. Microsoft Azure Cosmos DB vs. Riak TS

System Properties Comparison Brytlyt vs. LevelDB vs. Microsoft Azure Cosmos DB vs. Riak TS

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 fast key-value storage library that provides an ordered mapping from string keys to string values

Globally distributed, horizontally scalable, multi-model database service

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.38
Rank	#279	Overall
	#126	Relational DBMS

Score	2.75
Rank	#107	Overall
	#19	Key-value stores

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

Score	0.25
Rank	#308	Overall
	#26	Time Series DBMS

Website

brytlyt.io

github.com/google/leveldb

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.brytlyt.io

github.com/google/leveldb/blob/main/doc/index.md

learn.microsoft.com/azure/cosmos-db

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Brytlyt

Google

Microsoft

Open Source, formerly Basho Technologies

Initial release

2016

2011

2014

2015

Current release

5.0, August 2023

1.23, February 2021

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Open Source

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

C++

Erlang

Server operating systems

Linux
OS X
Windows

Illumos
Linux
OS X
Windows

hosted

Linux
OS X

Data scheme

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

restricted

SQL

Support of SQL

yes

SQL-like query language

yes, limited

APIs and other access methods

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

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

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

JavaScript

Erlang

Triggers

yes

JavaScript

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

Implicit feature of the cloud service

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

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

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

with automatic compression on writes

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.