DBMS > CockroachDB vs. Faircom EDGE vs. Firebird vs. RocksDB

System Properties Comparison CockroachDB vs. Faircom EDGE vs. Firebird vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Key-value store

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.cockroachlabs.com

www.faircom.com/products/faircom-edge

www.firebirdsql.org

rocksdb.org

Technical documentation

www.cockroachlabs.com/docs

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

www.firebirdsql.org/en/reference-manuals

github.com/facebook/rocksdb/wiki

Developer

Cockroach Labs

FairCom Corporation

Firebird Foundation

Facebook, Inc.

Initial release

2015

1979

2000

As fork of Borland's InterBase

2013

Current release

23.1.1, May 2023

V3, October 2020

5.0.0, January 2024

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Restricted, free version available

Open Source

Initial Developer's Public License

Open Source

BSD

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

ANSI C, C++

C and C++

C++

Server operating systems

Linux
macOS
Windows

Android
Linux

ARM, x86
Raspbian
Windows

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux

Data scheme

dynamic schema

Flexible Schema (defined schema, partial schema, schema free)

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL 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

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

ANSI SQL queries

yes

APIs and other access methods

JDBC

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

C++ API
Java API

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

PSQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

File partitioning

Customizable business rules for partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

yes

Synchronous and asynchronous realtime replication based on transaction logs

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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.

yes

User concepts

Access control

Role-based access control

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Users with fine-grained authorization concept

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.