DBMS > Amazon CloudSearch vs. Apache Druid vs. Microsoft SQL Server vs. XTDB

System Properties Comparison Amazon CloudSearch vs. Apache Druid vs. Microsoft SQL Server vs. XTDB

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Microsofts flagship relational DBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Search engine

Relational DBMS
Time Series DBMS

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

aws.amazon.com/cloudsearch

druid.apache.org

www.microsoft.com/en-us/sql-server

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/cloudsearch

druid.apache.org/docs/latest/design

learn.microsoft.com/en-US/sql/sql-server

www.xtdb.com/docs

Developer

Amazon

Apache Software Foundation and contributors

Microsoft

Juxt Ltd.

Initial release

2012

1989

2019

Current release

29.0.1, April 2024

SQL Server 2022, November 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

restricted free version is available

Open Source

MIT License

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

C++

Clojure

Server operating systems

hosted

Linux
OS X
Unix

Linux
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-less columns are supported

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

SQL for querying

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP API

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP REST
JDBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Clojure
Java

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

manual/auto, time-based

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes, via HDFS, S3 or other storage engines

yes, but depending on the SQL-Server Edition

yes, each node contains all data

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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.