DBMS > AlaSQL vs. Couchbase vs. etcd vs. Microsoft Access vs. Microsoft Azure SQL Database

System Properties Comparison AlaSQL vs. Couchbase vs. etcd vs. Microsoft Access vs. Microsoft Azure SQL Database

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

A distributed reliable key-value store

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

Primary database model

Document store
Relational DBMS

Document store

Key-value store

Relational DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Website

alasql.org

www.couchbase.com

etcd.io
github.com/etcd-io/etcd

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

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

Technical documentation

github.com/AlaSQL/alasql

docs.couchbase.com

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

developer.microsoft.com/en-us/access

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

Developer

Andrey Gershun & Mathias R. Wulff

Couchbase, Inc.

Microsoft

Initial release

2014

2011

1992

2010

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

3.4, August 2019

1902 (16.0.11328.20222), March 2019

V12

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

Apache Version 2.0

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, C++, Go and Erlang

C++

Server operating systems

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

Linux
OS X
Windows

FreeBSD
Linux
Windows

experimental

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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.

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JavaScript API

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

gRPC
JSON over HTTP

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC

Supported programming languages

JavaScript

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

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

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

since Access 2010 using the ACE-engine

Transact SQL

Triggers

yes

via the TAP protocol

yes, watching key changes

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

including cross data center replication
Source-replica replication

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

none

yes, with always 3 replicas available

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

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

Ephemeral buckets

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base 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.