DBMS > FoundationDB vs. GeoSpock vs. Interbase vs. Microsoft Access vs. SQLite

System Properties Comparison FoundationDB vs. GeoSpock vs. Interbase vs. Microsoft Access vs. SQLite

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Ordered key-value store. Core features are complimented by layers.

Spatial and temporal data processing engine for extreme data scale

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

Widely used embeddable, in-process RDBMS

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/apple/foundationdb

geospock.com

www.embarcadero.com/products/interbase

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

www.sqlite.org

Technical documentation

apple.github.io/foundationdb

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

www.sqlite.org/docs.html

Developer

FoundationDB

GeoSpock

Embarcadero

Microsoft

Dwayne Richard Hipp

Initial release

2013

1984

1992

2000

Current release

6.2.28, November 2020

2.0, September 2019

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

Public Domain

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++

Java, Javascript

C++

Server operating systems

Linux
OS X
Windows

hosted

Android
iOS
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

server-less

Data scheme

schema-free

some layers support schemas

yes

dynamic column types

Typing

predefined data types such as float or date

some layers support typing

yes

not rigid because of 'dynamic typing' concept.

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

temporal, categorical

yes

SQL

Support of SQL

supported in specific SQL layer only

ANSI SQL for query only (using Presto)

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

in SQL-layer only

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Interbase Change Views

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

via file-system locks

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 can be defined per table

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.