DBMS > AlaSQL vs. Dragonfly vs. Microsoft Access vs. Snowflake

System Properties Comparison AlaSQL vs. Dragonfly vs. Microsoft Access vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

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

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

Primary database model

Document store
Relational DBMS

Key-value store

Relational DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

alasql.org

github.com/dragonflydb/dragonfly
www.dragonflydb.io

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

www.snowflake.com

Technical documentation

github.com/AlaSQL/alasql

www.dragonflydb.io/docs

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

Andrey Gershun & Mathias R. Wulff

DragonflyDB team and community contributors

Microsoft

Snowflake Computing Inc.

Initial release

2014

2023

1992

2014

Current release

1.0, March 2023

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

MIT-License

Open Source

BSL 1.1

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

JavaScript

C++

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

schema-free

scheme-free

yes

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

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JavaScript API

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

JavaScript

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

publish/subscribe channels provide some trigger functionality

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

Atomic execution of command blocks and scripts

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

Password-based authentication

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.