DBMS > Faircom DB vs. Faircom EDGE vs. MySQL vs. Riak KV vs. Yanza

System Properties Comparison Faircom DB vs. Faircom EDGE vs. MySQL vs. Riak KV vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Widely used open source RDBMS

Distributed, fault tolerant key-value store

Time Series DBMS for IoT Applications

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Time Series DBMS

Secondary database models

Document store
Spatial 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.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

www.faircom.com/products/faircom-db

www.faircom.com/products/faircom-edge

www.mysql.com

yanza.com

Technical documentation

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

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

dev.mysql.com/doc

www.tiot.jp/riak-docs/riak/kv/latest

Developer

FairCom Corporation

Oracle

since 2010, originally MySQL AB, then Sun

OpenSource, formerly Basho Technologies

Yanza

Initial release

1979

1995

2009

2015

Current release

V12, November 2020

V3, October 2020

8.4.0, April 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Restricted, free version available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache version 2, commercial enterprise edition

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

ANSI C, C++

C and C++

Erlang

Server operating systems

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

easily portable to other OSs

Android
Linux

ARM, x86
Raspbian
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

Windows

Data scheme

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

Flexible Schema (defined schema, 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, 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

restricted

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

ANSI SQL queries

yes

with proprietary extensions

APIs and other access methods

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

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

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

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

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

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

.Net, JavaScript, C/C++

yes

proprietary syntax

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

File partitioning

Customizable business rules for partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

no "single point of failure"

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

yes

Synchronous and asynchronous realtime replication based on transaction logs

Multi-source replication
Source-replica replication

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency
Tunable Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

not for MyISAM storage engine

links between data sets can be stored

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

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

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

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

Users with fine-grained authorization concept

no user groups or roles

yes, using Riak Security

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.