DBMS > BigObject vs. Ehcache vs. Microsoft Access vs. Microsoft Azure SQL Database vs. SQLite

System Properties Comparison BigObject vs. Ehcache vs. Microsoft Access vs. Microsoft Azure SQL Database vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

A widely adopted Java cache with tiered storage options

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

bigobject.io

www.ehcache.org

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

azure.microsoft.com/en-us/products/azure-sql/database

www.sqlite.org

Technical documentation

docs.bigobject.io

www.ehcache.org/documentation

developer.microsoft.com/en-us/access

docs.microsoft.com/en-us/azure/azure-sql

www.sqlite.org/docs.html

Developer

BigObject, Inc.

Terracotta Inc, owned by Software AG

Microsoft

Dwayne Richard Hipp

Initial release

2015

2009

1992

2010

2000

Current release

3.10.0, March 2022

1902 (16.0.11328.20222), March 2019

V12

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache Version 2; commercial licenses available

commercial

Bundled with Microsoft Office

commercial

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

Java

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

hosted

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

JCache

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

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

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Lua

yes

since Access 2010 using the ACE-engine

Transact SQL

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

by using Terracotta Server

none

yes, with always 3 replicas available

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

via file-system locks

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

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

fine grained access rights according to SQL-standard

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.