DBMS > Firebird vs. HarperDB vs. Manticore Search vs. Microsoft Azure Cosmos DB

System Properties Comparison Firebird vs. HarperDB vs. Manticore Search vs. Microsoft Azure Cosmos DB

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Multi-storage database for search, including full-text search.

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Spatial DBMS

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

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

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

Website

www.firebirdsql.org

www.harperdb.io

manticoresearch.com

azure.microsoft.com/services/cosmos-db

Technical documentation

www.firebirdsql.org/en/reference-manuals

docs.harperdb.io/docs

manual.manticoresearch.com

learn.microsoft.com/azure/cosmos-db

Developer

Firebird Foundation

HarperDB

Manticore Software

Microsoft

Initial release

2000

As fork of Borland's InterBase

2017

2014

Current release

5.0.0, January 2024

3.1, August 2021

6.0, February 2023

License

Commercial or Open Source

Open Source

Initial Developer's Public License

commercial

free community edition available

Open Source

GPL version 2

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

Node.js

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux
OS X

FreeBSD
Linux
macOS
Windows

hosted

Data scheme

yes

dynamic schema

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like data manipulation statements

SQL-like query language

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

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

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

Server-side scripts

Stored procedures

PSQL

Custom Functions

since release 3.1

user defined functions

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

A table resides as a whole on one (or more) nodes in a cluster

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

the nodes on which a table resides can be defined

Synchronous replication based on Galera library

yes

Implicit feature of the cloud service

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

Immediate 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 execution of specific operations

yes

isolated transactions for atomic changes and binary logging for safe writes

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

Durability

Support for making data persistent

yes

yes, using LMDB

yes

The original contents of fields are not stored in the Manticore index.

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

Users with fine-grained authorization concept

Access rights for users and roles

Access rights can be defined down to the item level

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.