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

System Properties Comparison Elasticsearch 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 distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

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.elastic.co/elasticsearch

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

nsdb.io

www.snowflake.com

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

developer.microsoft.com/en-us/access

nsdb.io/Architecture

docs.snowflake.net/manuals/index.html

Developer

Elastic

Microsoft

Snowflake Computing Inc.

Initial release

2010

1992

2017

2014

Current release

8.6, January 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Elastic License

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

Flexible type definitions. Once a type is defined, it is persistent

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 search fields are automatically indexed

yes

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

yes

but not compliant to any SQL standard

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

gRPC
HTTP REST
WebSocket

CLI Client
JDBC
ODBC

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

by using the 'percolation' feature

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

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

Durability

Support for making data persistent

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.

Memcached and Redis integration

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.