DBMS > Faircom DB vs. Immudb vs. Machbase Neo vs. mSQL vs. RocksDB

System Properties Comparison Faircom DB vs. Immudb vs. Machbase Neo vs. mSQL vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

TimeSeries DBMS for AIoT and BigData

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

Primary database model

Key-value store
Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

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

Website

www.faircom.com/products/faircom-db

github.com/codenotary/immudb
immudb.io

machbase.com

hughestech.com.au/products/msql

rocksdb.org

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

docs.immudb.io

machbase.com/dbms

github.com/facebook/rocksdb/wiki

Developer

FairCom Corporation

Codenotary

Machbase

Hughes Technologies

Facebook, Inc.

Initial release

1979

2020

2013

1994

2013

Current release

V12, November 2020

1.2.3, April 2022

V8.0, August 2023

4.4, October 2021

8.11.4, April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache Version 2.0

commercial

free test version available

commercial

free licenses can be provided

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

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

BSD
Linux
macOS
Solaris
Windows
z/OS

Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux

Data scheme

schema free, schema optional, schema required, partial schema,

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

SQL-like syntax

SQL-like query language

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

gRPC protocol
PostgreSQL wire protocol

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

JDBC
ODBC

C++ API
Java API

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C++
Delphi
Java
Perl
PHP
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

selectable replication factor

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

yes

In-memory capabilities

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

yes

volatile and lookup table

yes

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

simple password-based access control

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.