DBMS > Faircom EDGE vs. Interbase vs. Microsoft Access vs. RocksDB

System Properties Comparison Faircom EDGE vs. Interbase vs. Microsoft Access vs. RocksDB

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

Light-weight proven RDBMS

originally from Borland

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.)

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key-value store

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	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.faircom.com/products/faircom-edge

www.embarcadero.com/products/interbase

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

rocksdb.org

Technical documentation

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

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

Developer

FairCom Corporation

Embarcadero

Microsoft

Facebook, Inc.

Initial release

1979

1984

1992

2013

Current release

V3, October 2020

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

8.11.4, April 2024

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Bundled with Microsoft Office

Open Source

BSD

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

Android
iOS
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

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

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

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

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

yes

but not compliant to any SQL standard

APIs and other access methods

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

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Supported programming languages

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

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

Interbase Change Views

none

yes

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

yes

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Multiversion concurreny control

yes

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

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

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

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.