DBMS > Faircom DB vs. Graphite vs. Ingres vs. Microsoft Azure Cosmos DB

System Properties Comparison Faircom DB vs. Graphite vs. Ingres vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Well established RDBMS

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

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

Website

www.faircom.com/products/faircom-db

github.com/graphite-project/graphite-web

www.actian.com/databases/ingres

azure.microsoft.com/services/cosmos-db

Technical documentation

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

graphite.readthedocs.io

docs.actian.com/ingres

learn.microsoft.com/azure/cosmos-db

Developer

FairCom Corporation

Chris Davis

Actian Corporation

Microsoft

Initial release

1979

2006

1974

originally developed at University Berkely in early 1970s

2014

Current release

V12, November 2020

11.2, May 2022

License

Commercial or Open Source

commercial

Restricted, free version available

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

Python

Server operating systems

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

easily portable to other OSs

Linux
Unix

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

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

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

Numeric data only

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

SQL-like query language

APIs and other access methods

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

HTTP API
Sockets

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

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

Supported programming languages

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

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Implicit feature of the cloud service

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

none

Ingres Replicator

yes

Implicit feature of the cloud service

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

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

none

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

tunable from ACID to Eventually Consistent

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

MVCC

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

User concepts

Access control

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

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.