DBMS > FatDB vs. HEAVY.AI vs. Microsoft Azure Cosmos DB vs. SAP SQL Anywhere

System Properties Comparison FatDB vs. HEAVY.AI vs. Microsoft Azure Cosmos DB vs. SAP SQL Anywhere

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.

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Globally distributed, horizontally scalable, multi-model database service

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

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

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

github.com/heavyai/heavydb
www.heavy.ai

azure.microsoft.com/services/cosmos-db

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.heavy.ai

learn.microsoft.com/azure/cosmos-db

help.sap.com/docs/SAP_SQL_Anywhere

Developer

FatCloud

HEAVY.AI, Inc.

Microsoft

SAP

formerly Sybase

Initial release

2012

2016

2014

1992

Current release

5.10, January 2022

17, July 2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

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++ and CUDA

Server operating systems

Windows

Linux

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

SQL-like query language

yes

APIs and other access methods

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

JDBC
ODBC
Thrift
Vega

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

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

JavaScript

yes, in C/C++, Java, .Net or Perl

Triggers

yes

via applications

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

yes

Implicit feature of the cloud service

Source-replica replication

Database mirroring

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

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

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

User concepts

Access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.