DBMS > Amazon CloudSearch vs. Brytlyt vs. Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB

System Properties Comparison Amazon CloudSearch vs. Brytlyt vs. Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

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

Search-as-a-service for web and mobile app development

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Search engine

Relational DBMS

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Vector DBMS

Spatial DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

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

Website

aws.amazon.com/cloudsearch

brytlyt.io

azure.microsoft.com/en-us/services/search

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.brytlyt.io

learn.microsoft.com/en-us/azure/search

learn.microsoft.com/azure/cosmos-db

Developer

Amazon

Brytlyt

Microsoft

Initial release

2012

2016

2015

2014

Current release

5.0, August 2023

License

Commercial or Open Source

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

Server operating systems

hosted

Linux
OS X
Windows

hosted

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 search fields are automatically indexed

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

HTTP API

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

.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

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

automatic partitioning across Amazon Search Instance as required

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Source-replica replication

yes

Implicit feature of the cloud service

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

In-memory capabilities

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

User concepts

Access control

authentication via encrypted signatures

fine grained access rights according to SQL-standard

yes

using Azure authentication

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.