DBMS > EXASOL vs. IBM Cloudant vs. Qdrant vs. Snowflake vs. Warp 10

System Properties Comparison EXASOL vs. IBM Cloudant vs. Qdrant vs. Snowflake vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering based on Apache CouchDB

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

Cloud-based data warehousing service for structured and semi-structured data

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.exasol.com

www.ibm.com/products/cloudant

github.com/qdrant/qdrant
qdrant.tech

www.snowflake.com

www.warp10.io

Technical documentation

www.exasol.com/resources

cloud.ibm.com/docs/Cloudant

qdrant.tech/documentation

docs.snowflake.net/manuals/index.html

www.warp10.io/content/02_Getting_started

Developer

Exasol

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Qdrant

Snowflake Computing Inc.

SenX

Initial release

2000

2010

2021

2014

2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Apache License 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

Erlang

Rust

Java

Server operating systems

hosted

Docker
Linux
macOS
Windows

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

CLI Client
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

Java
Lua
Python
R

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

View functions (Map-Reduce) in JavaScript

user defined functions

yes

WarpScript

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Collection-level replication

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency, tunable consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users, groups and roles according to SQL-standard

Access rights for users can be defined per database

Key-based authentication

Users with fine-grained authorization concept, user roles and pluggable authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.