DBMS > Amazon CloudSearch vs. ClickHouse vs. Google Cloud Datastore vs. Microsoft Azure Data Explorer vs. Teradata

System Properties Comparison Amazon CloudSearch vs. ClickHouse vs. Google Cloud Datastore vs. Microsoft Azure Data Explorer vs. Teradata

Editorial information provided by DB-Engines

Name

Description

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

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Fully managed big data interactive analytics platform

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

column oriented

Secondary database models

Time Series DBMS

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

aws.amazon.com/cloudsearch

clickhouse.com

cloud.google.com/datastore

azure.microsoft.com/services/data-explorer

www.teradata.com

Technical documentation

docs.aws.amazon.com/cloudsearch

clickhouse.com/docs

cloud.google.com/datastore/docs

docs.microsoft.com/en-us/azure/data-explorer

docs.teradata.com

Developer

Amazon

Clickhouse Inc.

Google

Microsoft

Teradata

Initial release

2012

2016

2008

2019

1984

Current release

v24.4.1.2088-stable, May 2024

cloud service with continuous releases

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

Server operating systems

hosted

FreeBSD
Linux
macOS

hosted

hosted
Linux

Data scheme

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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.

yes

Secondary indexes

yes

all search fields are automatically indexed

yes

all fields are automatically indexed

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (GQL)

Kusto Query Language (KQL), SQL subset

yes

SQL 2016 + extensions

APIs and other access methods

HTTP API

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

using Google App Engine

Yes, possible languages: KQL, Python, R

yes

UDFs, stored procedures, table functions in parallel

Triggers

Callbacks using the Google Apps Engine

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

key based and custom

Sharding

Implicit feature of the cloud service

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Multi-source replication using Paxos

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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 rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Azure Active Directory Authentication

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.