DBMS > Amazon CloudSearch vs. Apache Impala vs. Microsoft Azure Cosmos DB vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison Amazon CloudSearch vs. Apache Impala vs. Microsoft Azure Cosmos DB vs. SAP Advantage Database Server vs. Snowflake

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Analytic DBMS for Hadoop

Globally distributed, horizontally scalable, multi-model database service

Low-cost RDBMS with access to ISAM and FoxPro data structures

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Search engine

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store

Spatial DBMS

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

Score	1.86
Rank	#133	Overall
	#12	Search engines

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

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

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

aws.amazon.com/cloudsearch

impala.apache.org

azure.microsoft.com/services/cosmos-db

www.sap.com/products/advantage-database-server.html

www.snowflake.com

Technical documentation

docs.aws.amazon.com/cloudsearch

impala.apache.org/impala-docs.html

learn.microsoft.com/azure/cosmos-db

docs.snowflake.net/manuals/index.html

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Microsoft

Sybase, SAP

Snowflake Computing Inc.

Initial release

2012

2013

2014

1993

2014

Current release

4.1.0, June 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

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

Server operating systems

hosted

Linux

hosted

Linux
Windows

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

all search fields are automatically indexed

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

APIs and other access methods

HTTP API

JDBC
ODBC

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

JavaScript

yes

user defined functions

Triggers

JavaScript

yes

similar concept for controling cloud resources

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

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

selectable replication factor

yes

Implicit feature of the cloud service

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual 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

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.

caching of (temporary) tables can be configured

User concepts

Access control

authentication via encrypted signatures

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.