DBMS > BoltDB vs. Kinetica vs. Linter vs. Microsoft Azure Cosmos DB vs. OpenQM

System Properties Comparison BoltDB vs. Kinetica vs. Linter vs. Microsoft Azure Cosmos DB vs. OpenQM

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Fully vectorized database across both GPUs and CPUs

RDBMS for high security requirements

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Multivalue DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Spatial DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

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

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

github.com/boltdb/bolt

www.kinetica.com

linter.ru

azure.microsoft.com/services/cosmos-db

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

Technical documentation

docs.kinetica.com

learn.microsoft.com/azure/cosmos-db

Developer

Kinetica

relex.ru

Microsoft

Rocket Software, originally Martin Phillips

Initial release

2013

2012

1990

2014

1993

Current release

7.1, August 2021

3.4-12

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

GPLv2, extended commercial license available

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

C, C++

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

with some exceptions

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

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

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax with the possibility to convert from PL/SQL

JavaScript

yes

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

GPU vRAM or System RAM

User concepts

Access control

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.