DBMS > FatDB vs. Kinetica vs. Kingbase vs. Microsoft Azure Cosmos DB

System Properties Comparison FatDB vs. Kinetica vs. Kingbase vs. Microsoft Azure Cosmos DB

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.

Description

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

Fully vectorized database across both GPUs and CPUs

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

Spatial DBMS

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

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	0.50
Rank	#257	Overall
	#119	Relational DBMS

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

Website

www.kinetica.com

www.kingbase.com.cn

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.kinetica.com

learn.microsoft.com/azure/cosmos-db

Developer

FatCloud

Kinetica

BeiJing KINGBASE Information technologies inc.

Microsoft

Initial release

2012

1999

2014

Current release

7.1, August 2021

V8.0, August 2021

License

Commercial or Open Source

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

C, C++

C and Java

Server operating systems

Windows

Linux

Linux
Windows

hosted

Data scheme

schema-free

yes

schema-free

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

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like DML and DDL statements

Standard with numerous extensions

SQL-like query language

APIs and other access methods

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

JDBC
ODBC
RESTful HTTP API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

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

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

Server-side scripts

Stored procedures

yes

via applications

user defined functions

JavaScript

Triggers

yes

via applications

yes

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

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

Can implement custom security layer via applications

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.