DBMS > Faircom EDGE vs. Machbase Neo vs. OrigoDB vs. SQLite

System Properties Comparison Faircom EDGE vs. Machbase Neo vs. OrigoDB vs. SQLite

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

TimeSeries DBMS for AIoT and BigData

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.02
Rank	#370	Overall
	#55	Key-value stores
	#157	Relational DBMS

Score	0.07
Rank	#348	Overall
	#34	Time Series DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.faircom.com/products/faircom-edge

machbase.com

origodb.com

www.sqlite.org

Technical documentation

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

machbase.com/dbms

origodb.com/docs

www.sqlite.org/docs.html

Developer

FairCom Corporation

Machbase

Robert Friberg et al

Dwayne Richard Hipp

Initial release

1979

2013

2009

under the name LiveDB

2000

Current release

V3, October 2020

V8.0, August 2023

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

free test version available

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

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux
macOS
Windows

Linux
Windows

server-less

Data scheme

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

yes

dynamic column types

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

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

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

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

.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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
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

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

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

selectable replication factor

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

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

volatile and lookup table

yes

User concepts

Access control

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

simple password-based access control

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.