DBMS > Faircom EDGE vs. Prometheus vs. RocksDB vs. VoltDB

System Properties Comparison Faircom EDGE vs. Prometheus vs. RocksDB vs. VoltDB

Please select another system to include it in the comparison.

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

Open-source Time Series DBMS and monitoring system

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Key-value store

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	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.faircom.com/products/faircom-edge

prometheus.io

rocksdb.org

www.voltdb.com

Technical documentation

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

prometheus.io/docs

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

FairCom Corporation

Facebook, Inc.

VoltDB Inc.

Initial release

1979

2015

2013

2010

Current release

V3, October 2020

9.2.1, May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache 2.0

Open Source

BSD

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux
Windows

Linux

Linux
OS X

for development

Data scheme

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

yes

only a subset of SQL 99

APIs and other access methods

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

RESTful HTTP/JSON API

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

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

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

by Federation

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

none

Foreign keys

Referential integrity

yes

when using SQL

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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.

Users and roles with access to stored procedures

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.