DBMS > Amazon CloudSearch vs. Microsoft Azure Cosmos DB vs. Warp 10 vs. XTDB

System Properties Comparison Amazon CloudSearch vs. Microsoft Azure Cosmos DB vs. Warp 10 vs. XTDB

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

Globally distributed, horizontally scalable, multi-model database service

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Document store

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	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

aws.amazon.com/cloudsearch

azure.microsoft.com/services/cosmos-db

www.warp10.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/cloudsearch

learn.microsoft.com/azure/cosmos-db

www.warp10.io/content/02_Getting_started

www.xtdb.com/docs

Developer

Amazon

Microsoft

SenX

Juxt Ltd.

Initial release

2012

2014

2015

2019

Current release

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

MIT License

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

Java

Clojure

Server operating systems

hosted

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP API

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

HTTP API
Jupyter
WebSocket

HTTP REST
JDBC

Supported programming languages

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

Clojure
Java

Server-side scripts

Stored procedures

JavaScript

yes

WarpScript

Triggers

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

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

yes, each node contains all data

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

authentication via encrypted signatures

Access rights can be defined down to the item level

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.