DBMS > Brytlyt vs. Coveo vs. Microsoft Azure Cosmos DB vs. Sadas Engine

System Properties Comparison Brytlyt vs. Coveo vs. Microsoft Azure Cosmos DB vs. Sadas Engine

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Globally distributed, horizontally scalable, multi-model database service

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

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	2.11
Rank	#118	Overall
	#11	Search engines

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

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

brytlyt.io

www.coveo.com

azure.microsoft.com/services/cosmos-db

www.sadasengine.com

Technical documentation

docs.brytlyt.io

docs.coveo.com

learn.microsoft.com/azure/cosmos-db

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Brytlyt

Coveo

Microsoft

SADAS s.r.l.

Initial release

2016

2012

2014

2006

Current release

5.0, August 2023

8.0

License

Commercial or Open Source

commercial

free trial version available

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++

Server operating systems

Linux
OS X
Windows

hosted

AIX
Linux
Windows

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C#
Java
JavaScript
Python

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

.Net
C
C#
C++
Groovy
Java
PHP
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

yes

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

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

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

managed by 'Learn by Usage'

User concepts

Access control

fine grained access rights according to SQL-standard

granular access controls, API key management, content filters

Access rights can be defined down to the item level

Access rights for users, groups and roles according to SQL-standard

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.