DBMS > Amazon CloudSearch vs. Coveo vs. Microsoft Azure Cosmos DB vs. Trafodion

System Properties Comparison Amazon CloudSearch vs. Coveo vs. Microsoft Azure Cosmos DB vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Transactional SQL-on-Hadoop DBMS

Primary database model

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	1.81
Rank	#137	Overall
	#12	Search engines

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

Website

aws.amazon.com/cloudsearch

www.coveo.com

azure.microsoft.com/services/cosmos-db

trafodion.apache.org

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.coveo.com

learn.microsoft.com/azure/cosmos-db

trafodion.apache.org/documentation.html

Developer

Amazon

Coveo

Microsoft

Apache Software Foundation, originally developed by HP

Initial release

2012

2014

Current release

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Server operating systems

hosted

Linux

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.

Secondary indexes

yes

all search fields are automatically indexed

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

HTTP API

RESTful HTTP API

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

ADO.NET
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

JavaScript

Java Stored Procedures

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

yes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

Implicit feature of the cloud service

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via user defined functions and HBase

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

ACID

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

granular access controls, API key management, content filters

Access rights can be defined down to the item level

fine grained access rights 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.