DBMS > Firebird vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Transwarp StellarDB

System Properties Comparison Firebird vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Transwarp StellarDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Firebird is an open source RDBMS forked from Borland's InterBase

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

A distributed graph DBMS built for enterprise-level graph applications

Primary database model

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Secondary database models

Spatial DBMS

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

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

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

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Website

www.firebirdsql.org

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

www.transwarp.cn/en/product/stellardb

Technical documentation

www.firebirdsql.org/en/reference-manuals

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

Developer

Firebird Foundation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Transwarp

Initial release

2000

As fork of Borland's InterBase

2010

2014

Current release

5.0.0, January 2024

License

Commercial or Open Source

Open Source

Initial Developer's Public License

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

Erlang

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

RESTful HTTP/JSON API

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

OpenCypher

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

PSQL

View functions (Map-Reduce) in JavaScript

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

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

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

ACID

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

Optimistic locking

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.

User concepts

Access control

Users with fine-grained authorization concept

Access rights for users can be defined per database

Access rights can be defined down to the item level

yes

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.