DBMS > Faircom DB vs. MySQL vs. Realm vs. YottaDB

System Properties Comparison Faircom DB vs. MySQL vs. Realm vs. YottaDB

Please select another system to include it in the comparison.

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.

Widely used open source RDBMS

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

A fast and solid embedded Key-value store

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Document store

Key-value store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	0.18
Rank	#314	Overall
	#45	Key-value stores
	#141	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	7.18
Rank	#52	Overall
	#8	Document stores

Score	0.21
Rank	#309	Overall
	#43	Key-value stores

Website

www.faircom.com/products/faircom-db

www.mysql.com

realm.io

yottadb.com

Technical documentation

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

dev.mysql.com/doc

realm.io/docs

yottadb.com/resources/documentation

Developer

FairCom Corporation

Oracle

since 2010, originally MySQL AB, then Sun

Realm, acquired by MongoDB in May 2019

YottaDB, LLC

Initial release

1979

1995

2014

2001

Current release

V13, July 2024

9.0.0, July 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL 3.0

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

Server operating systems

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

easily portable to other OSs

FreeBSD
Linux
OS X
Solaris
Windows

Android
Backend: server-less
iOS
Windows

Docker
Linux

Data scheme

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

with proprietary extensions

by using the Octo plugin

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Java

with Android only
Objective-C
React Native
Swift

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

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).

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

not for MyISAM storage engine

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

In-Memory realm

yes

User concepts

Access control

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

Users with fine-grained authorization concept

no user groups or roles

yes

Users and groups based on OS-security mechanisms

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.