DBMS > Amazon CloudSearch vs. BoltDB vs. ClickHouse vs. Qdrant

System Properties Comparison Amazon CloudSearch vs. BoltDB vs. ClickHouse vs. Qdrant

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 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.

A high-performance vector database with neural network or semantic-based matching

Primary database model

Secondary database models

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	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

aws.amazon.com/cloudsearch

github.com/boltdb/bolt

clickhouse.com

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.aws.amazon.com/cloudsearch

clickhouse.com/docs

qdrant.tech/documentation

Developer

Amazon

Clickhouse Inc.

Qdrant

Initial release

2012

2013

2016

2021

Current release

v24.4.1.2088-stable, May 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Apache Version 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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
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.

Implementation language

C++

Rust

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

APIs and other access methods

HTTP API

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

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)
Python
Rust

Server-side scripts

Stored procedures

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

key based and custom

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

none

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

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

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.

Key-based authentication

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.