DBMS > Amazon CloudSearch vs. EXASOL vs. Interbase vs. Microsoft Azure Cosmos DB vs. Qdrant

System Properties Comparison Amazon CloudSearch vs. EXASOL vs. Interbase vs. Microsoft Azure Cosmos DB vs. Qdrant

Editorial information provided by DB-Engines

Name

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Light-weight proven RDBMS

originally from Borland

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Search engine

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Vector DBMS

Secondary database models

Spatial DBMS

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Website

aws.amazon.com/cloudsearch

www.exasol.com

www.embarcadero.com/products/interbase

azure.microsoft.com/services/cosmos-db

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.aws.amazon.com/cloudsearch

www.exasol.com/resources

docs.embarcadero.com/products/interbase

learn.microsoft.com/azure/cosmos-db

qdrant.tech/documentation

Developer

Amazon

Exasol

Embarcadero

Microsoft

Qdrant

Initial release

2012

2000

1984

2014

2021

Current release

InterBase 2020, December 2019

License

Commercial or Open Source

commercial

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.

Implementation language

Rust

Server operating systems

hosted

Android
iOS
Linux
OS X
Windows

hosted

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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.

export as XML data possible

Secondary indexes

yes

all search fields are automatically indexed

yes

All properties auto-indexed by default

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

HTTP API

.Net
JDBC
ODBC
WebSocket

ADO.NET
JDBC
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

Java
Lua
Python
R

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes

Interbase procedure and trigger language

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Interbase Change Views

yes

Implicit feature of the cloud service

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

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, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.