DBMS > Faircom EDGE vs. RocksDB vs. SiteWhere vs. Tarantool vs. TimesTen

System Properties Comparison Faircom EDGE vs. RocksDB vs. SiteWhere vs. Tarantool vs. TimesTen

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

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

M2M integration platform for persisting/querying time series data

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

In-Memory RDBMS compatible to Oracle

Primary database model

Key-value store
Relational DBMS

Key-value store

Time Series DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

www.faircom.com/products/faircom-edge

rocksdb.org

github.com/sitewhere/sitewhere

www.tarantool.io

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

Technical documentation

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

github.com/facebook/rocksdb/wiki

sitewhere1.sitewhere.io/index.html

www.tarantool.io/en/doc

docs.oracle.com/database/timesten-18.1

Developer

FairCom Corporation

Facebook, Inc.

SiteWhere

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

1979

2013

2010

2008

1998

Current release

V3, October 2020

9.2.1, May 2024

2.10.0, May 2022

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

BSD

Open Source

Common Public Attribution License Version 1.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

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

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux

Linux
OS X
Windows

BSD
Linux
macOS

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

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

schema-free

predefined scheme

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

SQL

Support of SQL

yes

ANSI SQL queries

Full-featured ANSI SQL support

yes

APIs and other access methods

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

C++ API
Java API

HTTP REST

Open binary protocol

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Lua, C and SQL stored procedures

PL/SQL

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

horizontal partitioning

Sharding

based on HBase

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

selectable replication factor

based on HBase

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

yes

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

by means of logfiles and checkpoints

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, full featured in-memory storage engine with persistence

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

fine grained access rights according to SQL-standard

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.