DBMS > Amazon CloudSearch vs. Amazon DynamoDB vs. PlanetScale vs. Trafodion

System Properties Comparison Amazon CloudSearch vs. Amazon DynamoDB vs. PlanetScale 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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Transactional SQL-on-Hadoop DBMS

Primary database model

Search engine

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

aws.amazon.com/cloudsearch

aws.amazon.com/dynamodb

planetscale.com

trafodion.apache.org

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.aws.amazon.com/dynamodb

planetscale.com/docs

trafodion.apache.org/documentation.html

Developer

Amazon

PlanetScale

Apache Software Foundation, originally developed by HP

Initial release

2012

2020

2014

Current release

2.3.0, February 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

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

Docker
Linux
macOS

Linux

Data scheme

yes

schema-free

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.

Secondary indexes

yes

all search fields are automatically indexed

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

HTTP API

RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

Java Stored Procedures

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

Multi-source replication
Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

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.