DBMS > BigchainDB vs. Microsoft Access vs. RDF4J

System Properties Comparison BigchainDB vs. Microsoft Access vs. RDF4J

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Document store

Relational DBMS

RDF store

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.77
Rank	#199	Overall
	#32	Document stores

Score	141.82
Rank	#9	Overall
	#6	Relational DBMS

Score	0.74
Rank	#206	Overall
	#9	RDF stores

Website

www.bigchaindb.com

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

rdf4j.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

developer.microsoft.com/en-us/access

rdf4j.org/documentation

Developer

Microsoft

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2016

1992

2004

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Bundled with Microsoft Office

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Python

C++

Java

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

Java
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

but no files for transaction logging

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

but no files for transaction logging

yes

in-memory storage is supported as well

User concepts

Access control

yes

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts