DBMS > Firebird vs. KeyDB vs. Microsoft Azure Cosmos DB vs. Realm

System Properties Comparison Firebird vs. KeyDB vs. Microsoft Azure Cosmos DB vs. Realm

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Globally distributed, horizontally scalable, multi-model database service

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Relational DBMS

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Spatial DBMS

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

Score	19.46
Rank	#30	Overall
	#18	Relational DBMS

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

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

Score	7.18
Rank	#52	Overall
	#8	Document stores

Website

www.firebirdsql.org

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/services/cosmos-db

realm.io

Technical documentation

www.firebirdsql.org/en/reference-manuals

docs.keydb.dev

learn.microsoft.com/azure/cosmos-db

realm.io/docs

Developer

Firebird Foundation

EQ Alpha Technology Ltd.

Microsoft

Realm, acquired by MongoDB in May 2019

Initial release

2000

As fork of Borland's InterBase

2019

2014

Current release

5.0.1, August 2024

License

Commercial or Open Source

Open Source

Initial Developer's Public License

Open Source

BSD-3

commercial

Open Source

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

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux

hosted

Android
Backend: server-less
iOS
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

Secondary indexes

yes

by using the Redis Search module

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

Proprietary protocol

RESP - REdis Serialization Protoco

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

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

PSQL

Lua

JavaScript

runs within the applications so server-side scripts are unnecessary

Triggers

yes

JavaScript

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

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

none

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
Strong eventual consistency with CRDTs

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Multi-item ACID transactions with snapshot isolation within a partition

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

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-Memory realm

User concepts

Access control

Users with fine-grained authorization concept

simple password-based access control and ACL

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.