DBMS > Faircom DB vs. IBM Cloudant vs. PostGIS

System Properties Comparison Faircom DB vs. IBM Cloudant vs. PostGIS

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.

Database as a Service offering based on Apache CouchDB

Spatial extension of PostgreSQL

Primary database model

Key-value store
Relational DBMS

Document store

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	0.22
Rank	#304	Overall
	#44	Key-value stores
	#137	Relational DBMS

Score	2.52
Rank	#99	Overall
	#18	Document stores

Score	18.94
Rank	#30	Overall
	#1	Spatial DBMS

Website

www.faircom.com/products/faircom-db

www.ibm.com/products/cloudant

postgis.net

Technical documentation

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

cloud.ibm.com/docs/Cloudant

postgis.net/documentation

Developer

FairCom Corporation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

1979

2010

2005

Current release

V13, July 2024

3.4.2, February 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

GPL v2.0

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

Erlang

Server operating systems

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

easily portable to other OSs

hosted

Data scheme

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

schema-free

yes

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

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

APIs and other access methods

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

RESTful HTTP/JSON API

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

yes

based on PostgreSQL

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

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

yes

based on PostgreSQL

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Motorola Solutions Strengthens FairCom Partnership Through FairCom Brazil Dev Day
20 February 2025, Business Wire

Trend-Setting Products in Data and Information Management for 2025
5 December 2024, Database Trends and Applications

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, IBM

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, IBM

IBM’s new CEO lays out his roadmap
6 May 2020, TechCentral.ie

provided by Google News

Share this page