DBMS > BigchainDB vs. dBASE vs. Microsoft Access vs. Realm vs. Snowflake

System Properties Comparison BigchainDB vs. dBASE vs. Microsoft Access vs. Realm vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.bigchaindb.com

www.dbase.com

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

realm.io

www.snowflake.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

developer.microsoft.com/en-us/access

realm.io/docs

docs.snowflake.net/manuals/index.html

Developer

Asthon Tate

Microsoft

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

Initial release

2016

1979

1992

2014

Current release

dBASE 2019, 2019

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Bundled with Microsoft Office

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Python

C++

Server operating systems

Linux

DOS

dBase Classic
Windows

dBase Pro

Windows

Not a real database server, but making use of DLLs

Android
Backend: server-less
iOS
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

dBase proprietary IDE

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

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

since Access 2010 using the ACE-engine

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

not for dBase internal data, but IDE does support transactions when accessing external DBMS

ACID

but no files for transaction logging

ACID

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 capabilities

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

yes

In-Memory realm

User concepts

Access control

yes

Access rights for users and roles

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

yes

Users with fine-grained authorization concept, user roles and pluggable authentication

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.