DBMS > Faircom EDGE vs. SiteWhere vs. SQLite vs. STSdb

System Properties Comparison Faircom EDGE vs. SiteWhere vs. SQLite vs. STSdb

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

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

Key-value store

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

Score	0.02
Rank	#370	Overall
	#55	Key-value stores
	#157	Relational DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

www.faircom.com/products/faircom-edge

github.com/sitewhere/sitewhere

www.sqlite.org

github.com/STSSoft/STSdb4

Technical documentation

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

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

FairCom Corporation

SiteWhere

Dwayne Richard Hipp

STS Soft SC

Initial release

1979

2010

2000

2011

Current release

V3, October 2020

3.46.1 (13 August 2024), August 2024

4.0.8, September 2015

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

Open Source

GPLv2, commercial license available

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

Java

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux
OS X
Windows

server-less

Windows

Data scheme

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

predefined scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

not rigid because of 'dynamic typing' concept.

yes

primitive types and user defined types (classes)

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

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

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API

Supported programming languages

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

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

C#
Java

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

selectable replication factor

based on HBase

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

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

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.

Users with fine-grained authorization concept

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.