DBMS > Faircom EDGE vs. Riak KV vs. ToroDB

System Properties Comparison Faircom EDGE vs. Riak KV vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

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

Distributed, fault tolerant key-value store

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Key-value store
Relational DBMS

Key-value store

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

Document store

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

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

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

Website

www.faircom.com/products/faircom-edge

github.com/torodb/server

Technical documentation

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

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

Developer

FairCom Corporation

OpenSource, formerly Basho Technologies

8Kdata

Initial release

1979

2009

2016

Current release

V3, October 2020

3.2.0, December 2022

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache version 2, commercial enterprise edition

Open Source

AGPL-V3

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

Erlang

Java

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux
OS X

All OS with a Java 7 VM

Data scheme

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

schema-free

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

string, integer, double, boolean, date, object_id

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 queries

APIs and other access methods

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

HTTP API
Native Erlang Interface

Supported programming languages

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

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

Erlang

Triggers

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

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

selectable replication factor

Source-replica replication

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

links between data sets can be stored

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

User concepts

Access control

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

yes, using Riak Security

Access rights for users and roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Innovative Software and Giant Lego Sets, Why FairCom Edge Booth is a Must-Visit at Automate
9 May 2024, MVPro

FairCom kicks off new era of database technology USA - English
10 November 2020, PR Newswire

Brokers, Protocols, Platform Move Manufacturing Data
26 July 2023, EE Times

Winners of the 2021 IoT Evolution Product of the Year Awards Announced
6 July 2021, IoT Evolution World

Trend-Setting Products in Data and Information Management for 2023
8 December 2022, Database Trends and Applications

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page