DBMS > FatDB vs. Qdrant vs. Riak KV vs. TempoIQ

System Properties Comparison FatDB vs. Qdrant vs. Riak KV vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Distributed, fault tolerant key-value store

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Document store
Key-value store

Vector DBMS

Key-value store

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

Time Series DBMS

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

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

github.com/qdrant/qdrant
qdrant.tech

tempoiq.com (offline)

Technical documentation

qdrant.tech/documentation

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

Developer

FatCloud

Qdrant

OpenSource, formerly Basho Technologies

TempoIQ

Initial release

2012

2021

2009

2012

Current release

3.2.0, December 2022

License

Commercial or Open Source

commercial

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

Windows

Docker
Linux
macOS
Windows

Linux
OS X

Data scheme

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.

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

restricted

SQL

Support of SQL

Via inetgration in SQL Server

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

HTTP API
Native Erlang Interface

HTTP API

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

Erlang

Triggers

yes

via applications

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Collection-level replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency, tunable consistency

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

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

Can implement custom security layer via applications

Key-based authentication

yes, using Riak Security

simple authentication-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Open source vector database startup Qdrant raises $28M
23 January 2024, TechCrunch

Qdrant Raises $28M to Advance Massive-Scale AI Applications
23 January 2024, businesswire.com

Qdrant Hybrid Cloud is Now Available for OCI Customers: Managed Vector Search Engine for Data-Sensitive AI ...
16 April 2024, blogs.oracle.com

Qdrant offers managed vector database for hybrid clouds
16 April 2024, InfoWorld

Why Vector Data Services For AI Are A Moveable Feast
17 April 2024, Forbes

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho launches complete NoSQL software kit - DCD
28 May 2015, DatacenterDynamics

provided by Google News

Share this page