DBMS > Faircom EDGE vs. MySQL vs. NuoDB vs. Oracle Berkeley DB vs. Riak TS

System Properties Comparison Faircom EDGE vs. MySQL vs. NuoDB vs. Oracle Berkeley DB vs. Riak TS

Editorial information provided by DB-Engines

Name

Description

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

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Widely used in-process key-value store

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.94
Rank	#197	Overall
	#92	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

www.faircom.com/products/faircom-edge

www.mysql.com

www.3ds.com/nuodb-distributed-sql-database

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

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

dev.mysql.com/doc

doc.nuodb.com

docs.oracle.com/cd/E17076_05/html/index.html

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

Developer

FairCom Corporation

Oracle

since 2010, originally MySQL AB, then Sun

Dassault Systèmes

originally NuoDB, Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Open Source, formerly Basho Technologies

Initial release

1979

1995

2013

1994

2015

Current release

V3, October 2020

8.4.0, April 2024

18.1.40, May 2020

3.0.0, September 2022

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

limited edition free

Open Source

commercial license available

Open Source

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.

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

C++

C, Java, C++ (depending on the Berkeley DB edition)

Erlang

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X

Data scheme

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

yes

schema-free

Typing

predefined data types such as float or date

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

only with the Berkeley DB XML edition

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

ANSI SQL queries

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

yes, limited

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

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

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

proprietary syntax

Java, SQL

Erlang

Triggers

yes

only for the SQL API

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

data is dynamically stored/cached on the nodes where it is read/written

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

Multi-source replication
Source-replica replication

yes

Managed transparently by NuoDB

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

not for MyISAM storage engine

yes

links between datasets can be stored

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

tunable commit protocol

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

table locks or row locks depending on storage engine

yes

MVCC

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

Temporary table

yes

User concepts

Access control

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

Standard SQL roles/ privileges, Administrative Users

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.