DBMS > Faircom EDGE vs. IRONdb vs. OrigoDB vs. SQLite

System Properties Comparison Faircom EDGE vs. IRONdb vs. OrigoDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

A fully ACID in-memory object graph database

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

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	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.faircom.com/products/faircom-edge

www.circonus.com/solutions/time-series-database/

origodb.com

www.sqlite.org

Technical documentation

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

docs.circonus.com/irondb/category/getting-started

origodb.com/docs

www.sqlite.org/docs.html

Developer

FairCom Corporation

Circonus LLC.

Robert Friberg et al

Dwayne Richard Hipp

Initial release

1979

2017

2009

under the name LiveDB

2000

Current release

V3, October 2020

V0.10.20, January 2018

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

Public Domain

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

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux

Linux
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

text, numeric, histograms

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

SQL-like query language (Circonus Analytics Query Language: CAQL)

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 API

.NET Client API
HTTP API
LINQ

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes, in Lua

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Automatic, metric affinity per node

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

configurable replication factor, datacenter aware

Source-replica replication

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 per node, eventual consistency across nodes

Foreign keys

Referential integrity

yes

when using SQL

depending on model

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

Write ahead log

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.

Role based authorization

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.