DBMS > Brytlyt vs. CouchDB vs. Datomic vs. Microsoft Azure Cosmos DB

System Properties Comparison Brytlyt vs. CouchDB vs. Datomic 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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

using the Geocouch extension

Spatial DBMS

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

Score	0.38
Rank	#276	Overall
	#127	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

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

Website

brytlyt.io

couchdb.apache.org

www.datomic.com

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.brytlyt.io

docs.couchdb.org/en/stable

docs.datomic.com

learn.microsoft.com/azure/cosmos-db

Developer

Brytlyt

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Cognitect

Microsoft

Initial release

2016

2005

2012

2014

Current release

5.0, August 2023

3.3.3, December 2023

1.0.7075, December 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

limited edition free

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

Erlang

Java, Clojure

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

hosted

Data scheme

yes

schema-free

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

via views

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

RESTful HTTP/JSON API

RESTful HTTP API

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

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Clojure
Java

.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

View functions in JavaScript

yes

Transaction Functions

JavaScript

Triggers

yes

By using transaction functions

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

But extensive use of caching in the application peers

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

none

But extensive use of caching in the application peers

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

atomic operations within a single document possible

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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.