DBMS > Faircom EDGE vs. Oracle Berkeley DB vs. Percona Server for MongoDB vs. Riak KV vs. Snowflake

System Properties Comparison Faircom EDGE vs. Oracle Berkeley DB vs. Percona Server for MongoDB vs. Riak KV vs. Snowflake

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 in-process key-value store

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Distributed, fault tolerant key-value store

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key-value store
Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

Key-value store

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

Relational 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	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.faircom.com/products/faircom-edge

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

www.percona.com/mongodb/software/percona-server-for-mongodb

www.snowflake.com

Technical documentation

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

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

docs.percona.com/percona-distribution-for-mongodb

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

docs.snowflake.net/manuals/index.html

Developer

FairCom Corporation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Percona

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

1979

1994

2015

2009

2014

Current release

V3, October 2020

18.1.40, May 2020

3.4.10-2.10, November 2017

3.2.0, December 2022

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

commercial license available

Open Source

GPL Version 2

Open Source

Apache version 2, commercial enterprise edition

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

ANSI C, C++

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

C++

Erlang

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Linux
OS X

hosted

Data scheme

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

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

ANSI SQL queries

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

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

proprietary protocol using JSON

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

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

.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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

JavaScript

Erlang

user defined functions

Triggers

yes

only for the SQL API

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

none

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

Source-replica replication

selectable replication factor

yes

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

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

links between data sets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

via In-Memory Engine

User concepts

Access control

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

Access rights for users and roles

yes, using Riak Security

Users with fine-grained authorization concept, user roles and pluggable authentication

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.