DBMS > Amazon CloudSearch vs. RavenDB vs. Snowflake vs. Teradata

System Properties Comparison Amazon CloudSearch vs. RavenDB vs. Snowflake vs. Teradata

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Search engine

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.86
Rank	#133	Overall
	#12	Search engines

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Website

aws.amazon.com/cloudsearch

ravendb.net

www.snowflake.com

www.teradata.com

Technical documentation

docs.aws.amazon.com/cloudsearch

ravendb.net/docs

docs.snowflake.net/manuals/index.html

docs.teradata.com

Developer

Amazon

Hibernating Rhinos

Snowflake Computing Inc.

Teradata

Initial release

2012

2010

2014

1984

Current release

5.4, July 2022

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

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

Server operating systems

hosted

Linux
macOS
Raspberry Pi
Windows

hosted

hosted
Linux

Data scheme

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL-like query language (RQL)

yes

SQL 2016 + extensions

APIs and other access methods

HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

CLI Client
JDBC
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

yes

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

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.

yes

User concepts

Access control

authentication via encrypted signatures

Authorization levels configured per client per database

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

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.