DBMS > Faircom DB vs. OpenQM vs. Qdrant vs. RocksDB

System Properties Comparison Faircom DB vs. OpenQM vs. Qdrant vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

QpenQM is a high-performance, self-tuning, multi-value DBMS

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store
Relational DBMS

Multivalue DBMS

Vector DBMS

Key-value store

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

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	1.28
Rank	#167	Overall
	#8	Vector DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.faircom.com/products/faircom-db

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

github.com/qdrant/qdrant
qdrant.tech

rocksdb.org

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

qdrant.tech/documentation

github.com/facebook/rocksdb/wiki

Developer

FairCom Corporation

Rocket Software, originally Martin Phillips

Qdrant

Facebook, Inc.

Initial release

1979

1993

2021

2013

Current release

V12, November 2020

3.4-12

9.2.1, May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

GPLv2, extended commercial license available

Open Source

Apache Version 2.0

Open Source

BSD

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

ANSI C, C++

Rust

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Docker
Linux
macOS
Windows

Linux

Data scheme

schema free, schema optional, schema required, partial schema,

yes

with some exceptions

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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.

yes

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

C++ API
Java API

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
Basic
C
Java
Objective C
PHP
Python

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

Collection-level replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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

Fine grained access rights according to SQL-standard with additional protections for files

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.