DBMS > Geode vs. Interbase vs. Microsoft Access vs. RocksDB

System Properties Comparison Geode 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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Key-value store

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

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

geode.apache.org

www.embarcadero.com/products/interbase

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

rocksdb.org

Technical documentation

geode.apache.org/docs

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Embarcadero

Microsoft

Facebook, Inc.

Initial release

2002

1984

1992

2013

Current release

1.1, February 2017

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

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

SQL-like query language (OQL)

yes

but not compliant to any SQL standard

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

.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

user defined functions

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

Triggers

yes

Cache Event Listeners

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

Multi-source replication

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

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 per client and object definable

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.