DBMS > Ehcache vs. Microsoft Access vs. NSDb vs. Snowflake

System Properties Comparison Ehcache vs. Microsoft Access vs. NSDb vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.ehcache.org

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

nsdb.io

www.snowflake.com

Technical documentation

www.ehcache.org/documentation

developer.microsoft.com/en-us/access

nsdb.io/Architecture

docs.snowflake.net/manuals/index.html

Developer

Terracotta Inc, owned by Software AG

Microsoft

Snowflake Computing Inc.

Initial release

2009

1992

2017

2014

Current release

3.10.0, March 2022

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2.0

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

Java

C++

Java, Scala

Server operating systems

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

Linux
macOS

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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.

yes

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

yes

APIs and other access methods

JCache

ADO.NET
DAO
ODBC
OLE DB

gRPC
HTTP REST
WebSocket

CLI Client
JDBC
ODBC

Supported programming languages

Java

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

Java
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

but no files for transaction logging

Using Apache Lucene

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.