DBMS > Amazon CloudSearch vs. Datomic vs. Google BigQuery vs. SwayDB vs. TimescaleDB

System Properties Comparison Amazon CloudSearch vs. Datomic vs. Google BigQuery vs. SwayDB vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Large scale data warehouse service with append-only tables

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

aws.amazon.com/cloudsearch

www.datomic.com

cloud.google.com/bigquery

swaydb.simer.au

www.timescale.com

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.datomic.com

cloud.google.com/bigquery/docs

docs.timescale.com

Developer

Amazon

Cognitect

Google

Simer Plaha

Timescale

Initial release

2012

2010

2018

2017

Current release

1.0.7075, December 2023

2.15.0, May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

GNU Affero GPL V3.0

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

Java, Clojure

Scala

Server operating systems

hosted

All OS with a Java VM

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

HTTP API

RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Clojure
Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Kotlin
Scala

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

But extensive use of caching in the application peers

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

none

But extensive use of caching in the application peers

none

Source-replica replication with hot standby and reads on replicas

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

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

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)

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.