DBMS > Faircom EDGE vs. GridDB vs. jBASE vs. Microsoft Access vs. Oracle

System Properties Comparison Faircom EDGE vs. GridDB vs. jBASE vs. Microsoft Access vs. Oracle

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

Scalable in-memory time series database optimized for IoT and Big Data

A robust multi-value DBMS comprising development tools and middleware

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

Widely used RDBMS

Primary database model

Key-value store
Relational DBMS

Time Series DBMS

Multivalue DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	1.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Website

www.faircom.com/products/faircom-edge

griddb.net

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

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

www.oracle.com/database

Technical documentation

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

docs.griddb.net

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

developer.microsoft.com/en-us/access

docs.oracle.com/en/database

Developer

FairCom Corporation

Toshiba Corporation

Rocket Software (formerly Zumasys)

Microsoft

Oracle

Initial release

1979

2013

1991

1992

1980

Current release

V3, October 2020

5.1, August 2022

5.7

1902 (16.0.11328.20222), March 2019

23c, September 2023

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Bundled with Microsoft Office

commercial

restricted free version is 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++

C++

C and C++

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux

AIX
Linux
Windows

Windows

Not a real database server, but making use of DLLs

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

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

yes

schema-free

yes

Schemaless in JSON and XML columns

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

numerical, string, blob, geometry, boolean, timestamp

optional

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

Secondary indexes

yes

SQL

Support of SQL

yes

ANSI SQL queries

SQL92, SQL-like TQL (Toshiba Query Language)

Embedded SQL for jBASE in BASIC

yes

but not compliant to any SQL standard

yes

with proprietary extensions

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
Basic
Jabbascript
Java

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

since Access 2010 using the ACE-engine

PL/SQL

also stored procedures in Java possible

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

none

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

Source-replica replication

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Immediate consistency within container, eventual consistency across containers

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

ACID at container level

ACID

but no files for transaction logging

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

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

Access rights for users can be defined per database

Access rights can be defined down to the item level

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

fine grained access rights according to SQL-standard

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.