DBMS > Amazon CloudSearch vs. Amazon DynamoDB vs. EsgynDB vs. OrigoDB vs. TerarkDB

System Properties Comparison Amazon CloudSearch vs. Amazon DynamoDB vs. EsgynDB vs. OrigoDB vs. TerarkDB

Editorial information provided by DB-Engines

Name

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A fully ACID in-memory object graph database

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Search engine

Document store
Key-value store

Relational DBMS

Document store
Object oriented DBMS

Key-value store

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

aws.amazon.com/cloudsearch

aws.amazon.com/dynamodb

www.esgyn.cn

origodb.com

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.aws.amazon.com/dynamodb

origodb.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon

Esgyn

Robert Friberg et al

ByteDance, originally Terark

Initial release

2012

2015

2009

under the name LiveDB

2016

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

commercial

restricted open source version available

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

C++

Server operating systems

hosted

Linux

Linux
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

all search fields are automatically indexed

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API

RESTful HTTP API

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

.Net

C++
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

Multi-source replication between multi datacenters

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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)

fine grained access rights according to SQL-standard

Role based authorization

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.