DBMS > Qdrant vs. Riak KV vs. Snowflake

System Properties Comparison Qdrant vs. Riak KV vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed, fault tolerant key-value store

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

Primary database model

Vector DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/qdrant/qdrant
qdrant.tech

www.snowflake.com

Technical documentation

qdrant.tech/documentation

www.tiot.jp/riak-docs/riak/kv/latest

docs.snowflake.net/manuals/index.html

Developer

Qdrant

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2021

2009

2014

Current release

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2, commercial enterprise edition

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.

Implementation language

Rust

Erlang

Server operating systems

Docker
Linux
macOS
Windows

Linux
OS X

hosted

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Collection-level replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency, tunable consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Key-based authentication

yes, using Riak Security

Users with fine-grained authorization concept, user roles and pluggable 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.