DBMS > Faircom EDGE vs. Heroic vs. IBM Db2 warehouse vs. SAP SQL Anywhere vs. SQLite

System Properties Comparison Faircom EDGE vs. Heroic vs. IBM Db2 warehouse vs. SAP SQL Anywhere vs. SQLite

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Cloud-based data warehousing service

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.faircom.com/products/faircom-edge

github.com/spotify/heroic

www.ibm.com/products/db2/warehouse

www.sap.com/products/technology-platform/sql-anywhere.html

www.sqlite.org

Technical documentation

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

spotify.github.io/heroic

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

Developer

FairCom Corporation

Spotify

IBM

SAP

formerly Sybase

Dwayne Richard Hipp

Initial release

1979

2014

1992

2000

Current release

V3, October 2020

17, July 2015

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache 2.0

commercial

Open Source

Public Domain

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

Java

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

Data scheme

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

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

not rigid because of 'dynamic typing' concept.

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/export of XML data possible

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

ANSI SQL queries

yes

SQL-92 is not fully supported

APIs and other access methods

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

PL/SQL, SQL PL

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

Source-replica replication

Database mirroring

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

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

via file-system locks

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.

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.