DBMS > Faircom EDGE vs. Microsoft Access vs. Realm vs. SQLite

System Properties Comparison Faircom EDGE vs. Microsoft Access vs. Realm 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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Document store

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	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.faircom.com/products/faircom-edge

www.microsoft.com/en-us/microsoft-365/access

realm.io

www.sqlite.org

Technical documentation

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

developer.microsoft.com/en-us/access

realm.io/docs

www.sqlite.org/docs.html

Developer

FairCom Corporation

Microsoft

Realm, acquired by MongoDB in May 2019

Dwayne Richard Hipp

Initial release

1979

1992

2014

2000

Current release

V3, October 2020

1902 (16.0.11328.20222), March 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Bundled with Microsoft Office

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

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Windows

Not a real database server, but making use of DLLs

Android
Backend: server-less
iOS
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

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

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

yes

but not compliant to any SQL standard

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

ADO.NET
DAO
ODBC
OLE DB

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++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

.Net
Java

with Android only
Objective-C
React Native
Swift

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

since Access 2010 using the ACE-engine

runs within the applications so server-side scripts are unnecessary

Triggers

yes

since Access 2010 using the ACE-engine

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

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

but no files for transaction logging

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

but no files for transaction logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-Memory realm

yes

User concepts

Access control

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

a simple user-level security was built in till version Access 2003

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.