DBMS > Google Cloud Bigtable vs. Interbase vs. Microsoft Access vs. RocksDB

System Properties Comparison Google Cloud Bigtable 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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

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
Wide column store

Relational DBMS

Key-value store

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

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	5.04
Rank	#71	Overall
	#39	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

cloud.google.com/bigtable

www.embarcadero.com/products/interbase

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

rocksdb.org

Technical documentation

cloud.google.com/bigtable/docs

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

Developer

Google

Embarcadero

Microsoft

Facebook, Inc.

Initial release

2015

1984

1992

2013

Current release

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

8.11.4, April 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

BSD

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

C++

Server operating systems

hosted

Android
iOS
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

schema-free

yes

schema-free

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.

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

.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

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

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

Interbase Change Views

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

but no files for transaction logging

yes

Concurrency

Support for concurrent manipulation of data

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.