DBMS > Firebird vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Newts vs. OpenEdge

System Properties Comparison Firebird vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. Newts vs. OpenEdge

Editorial information provided by DB-Engines

Name

Description

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

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

Time Series DBMS based on Cassandra

Application development environment with integrated database management system

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Time Series DBMS

Relational 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	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Website

www.firebirdsql.org

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

opennms.github.io/newts

www.progress.com/openedge

Technical documentation

www.firebirdsql.org/en/reference-manuals

learn.microsoft.com/azure/cosmos-db

github.com/OpenNMS/newts/wiki

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Firebird Foundation

Microsoft

OpenNMS Group

Progress Software Corporation

Initial release

2000

As fork of Borland's InterBase

2014

2012

2014

1984

Current release

5.0.0, January 2024

OpenEdge 12.2, March 2020

License

Commercial or Open Source

Open Source

Initial Developer's Public License

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

C and C++

Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

close to SQL 92

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

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

RESTful HTTP API

HTTP REST
Java API

JDBC
ODBC

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

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

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

Java

Progress proprietary ABL (Advanced Business Language)

Server-side scripts

Stored procedures

PSQL

JavaScript

yes

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

based on Cassandra

horizontal partitioning

since Version 11.4

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

selectable replication factor

based on Cassandra

Source-replica replication

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

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 can be defined down to the item level

Access rights based on private key authentication or shared access signatures

Users and groups

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.