DBMS > Faircom EDGE vs. SAP HANA vs. YugabyteDB

System Properties Comparison Faircom EDGE vs. SAP HANA vs. YugabyteDB

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

In-memory, column based data store. Available as appliance or cloud service

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Wide column store

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

Score	0.01
Rank	#384	Overall
	#59	Key-value stores
	#157	Relational DBMS

Score	37.65
Rank	#22	Overall
	#15	Relational DBMS

Score	2.45
Rank	#107	Overall
	#53	Relational DBMS

Website

www.faircom.com/products/faircom-edge

www.sap.com/products/hana.html

www.yugabyte.com

Technical documentation

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

help.sap.com/hana

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

FairCom Corporation

SAP

Yugabyte Inc.

Initial release

1979

2010

2017

Current release

V3, October 2020

2.0 SPS07 (April 4, 2023), April 2023

2.19, September 2023

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based 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 and C++

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Appliance or cloud-service

Linux
OS X

Data scheme

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

yes

depending on used data model

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

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

yes

yes, PostgreSQL compatible

APIs and other access methods

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

JDBC
ODBC

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

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

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust
Scala

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

SQLScript, R

yes

sql, plpgsql, C

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

yes

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

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

Strong consistency on writes and tunable consistency on reads

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Durability

Support for making data persistent

yes

based on RocksDB

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

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.