DBMS > FatDB vs. GigaSpaces vs. Microsoft Azure Cosmos DB vs. Quasardb

System Properties Comparison FatDB vs. GigaSpaces vs. Microsoft Azure Cosmos DB vs. Quasardb

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.

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Globally distributed, horizontally scalable, multi-model database service

Distributed, high-performance timeseries database

Primary database model

Document store
Key-value store

Document store
Object oriented DBMS

Values are user defined objects

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Graph DBMS
Search engine

Spatial DBMS

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

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

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

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

www.gigaspaces.com

azure.microsoft.com/services/cosmos-db

quasar.ai

Technical documentation

docs.gigaspaces.com/latest/landing.html

learn.microsoft.com/azure/cosmos-db

doc.quasar.ai/master

Developer

FatCloud

Gigaspaces Technologies

Microsoft

quasardb

Initial release

2012

2000

2014

2009

Current release

15.5, September 2020

3.14.1, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; Commercial licenses available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Java, C++, .Net

C++

Server operating systems

Windows

Linux
macOS
Solaris
Windows

hosted

BSD
Linux
OS X
Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

integer and binary

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.

XML can be used for describing objects metadata

Secondary indexes

yes

All properties auto-indexed by default

yes

with tags

SQL

Support of SQL

Via inetgration in SQL Server

SQL-99 for query and DML statements

SQL-like query language

APIs and other access methods

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

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

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

HTTP API

Supported programming languages

.Net
C++
Java
Python
Scala

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

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

Server-side scripts

Stored procedures

yes

via applications

yes

JavaScript

Triggers

yes

via applications

yes, event driven architecture

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

Implicit feature of the cloud service

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

by using LevelDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

User concepts

Access control

Can implement custom security layer via applications

Role-based access control

Access rights can be defined down to the item level

Cryptographically strong user authentication and audit trail

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.