DBMS > Amazon CloudSearch vs. Apache Phoenix vs. Google BigQuery vs. Riak TS

System Properties Comparison Amazon CloudSearch vs. Apache Phoenix vs. Google BigQuery vs. Riak TS

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

Large scale data warehouse service with append-only tables

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Search engine

Relational DBMS

Time Series DBMS

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

aws.amazon.com/cloudsearch

phoenix.apache.org

cloud.google.com/bigquery

Technical documentation

docs.aws.amazon.com/cloudsearch

phoenix.apache.org

cloud.google.com/bigquery/docs

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Amazon

Apache Software Foundation

Google

Open Source, formerly Basho Technologies

Initial release

2012

2014

2010

2015

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

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

Java

Erlang

Server operating systems

hosted

Linux
Unix
Windows

hosted

Linux
OS X

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

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

restricted

SQL

Support of SQL

yes

yes, limited

APIs and other access methods

HTTP API

JDBC

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication
Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

Google Cloud Identity & Access Management (IAM)

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.