DBMS > Amazon CloudSearch vs. EJDB vs. Google BigQuery vs. Transwarp KunDB

System Properties Comparison Amazon CloudSearch vs. EJDB vs. Google BigQuery vs. Transwarp KunDB

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Large scale data warehouse service with append-only tables

OLTP DBMS based on a distributed architecture and highly compatible with MySQL and Oracle

Primary database model

Search engine

Document store

Relational DBMS

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.14
Rank	#341	Overall
	#149	Relational DBMS

Website

aws.amazon.com/cloudsearch

github.com/Softmotions/ejdb

cloud.google.com/bigquery

www.transwarp.cn/en/product/kundb

Technical documentation

docs.aws.amazon.com/cloudsearch

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/bigquery/docs

Developer

Amazon

Softmotions

Google

Transwarp

Initial release

2012

2010

License

Commercial or Open Source

commercial

Open Source

GPLv2

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

server-less

hosted

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

APIs and other access methods

HTTP API

in-process shared library

RESTful HTTP/JSON API

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

User concepts

Access control

authentication via encrypted signatures

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes

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.