DBMS > EJDB vs. Memcached vs. Microsoft Access vs. Microsoft Azure Cosmos DB

System Properties Comparison EJDB vs. Memcached vs. Microsoft Access vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

In-memory key-value store, originally intended for caching

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

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store

Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

github.com/Softmotions/ejdb

www.memcached.org

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

azure.microsoft.com/services/cosmos-db

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

github.com/memcached/memcached/wiki

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

Developer

Softmotions

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Initial release

2012

2003

1992

2014

Current release

1.6.25, March 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

GPLv2

Open Source

BSD license

commercial

Bundled with Microsoft Office

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

C++

Server operating systems

server-less

FreeBSD
Linux
OS X
Unix
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

in-process shared library

Proprietary protocol

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

none

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

User concepts

Access control

yes

using SASL (Simple Authentication and Security Layer) protocol

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

Access rights can be defined down to the item level

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.