DBMS > Faircom DB vs. FatDB vs. Heroic vs. SAP Advantage Database Server vs. Snowflake

System Properties Comparison Faircom DB vs. FatDB vs. Heroic vs. SAP Advantage Database Server vs. Snowflake

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.

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Low-cost RDBMS with access to ISAM and FoxPro data structures

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key-value store
Relational DBMS

Document store
Key-value store

Time Series DBMS

Relational DBMS

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

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.faircom.com/products/faircom-db

github.com/spotify/heroic

www.sap.com/products/advantage-database-server.html

www.snowflake.com

Technical documentation

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

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

Developer

FairCom Corporation

FatCloud

Spotify

Sybase, SAP

Snowflake Computing Inc.

Initial release

1979

2012

2014

1993

2014

Current release

V13, July 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

Apache 2.0

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

ANSI C, C++

Java

Server operating systems

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

easily portable to other OSs

Windows

Linux
Windows

hosted

Data scheme

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

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

via Elasticsearch

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

Via inetgration in SQL Server

yes

APIs and other access methods

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

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

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

Delphi
Perl
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

via applications

yes

user defined functions

Triggers

yes

via applications

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

none

yes

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).

selectable replication factor

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Eventual Consistency
Immediate Consistency

Immediate 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

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

caching of (temporary) tables can be configured

User concepts

Access control

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

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable 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.