DBMS > Couchbase vs. EsgynDB vs. Microsoft Access vs. ToroDB vs. Yanza

System Properties Comparison Couchbase vs. EsgynDB vs. Microsoft Access vs. ToroDB vs. Yanza

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Time Series DBMS for IoT Applications

Primary database model

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

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

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

www.couchbase.com

www.esgyn.cn

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

github.com/torodb/server

yanza.com

Technical documentation

docs.couchbase.com

developer.microsoft.com/en-us/access

Developer

Couchbase, Inc.

Esgyn

Microsoft

8Kdata

Yanza

Initial release

2011

2015

1992

2016

2015

Current release

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

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

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

commercial

Bundled with Microsoft Office

Open Source

AGPL-V3

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++, Go and Erlang

C++, Java

C++

Java

Server operating systems

Linux
OS X
Windows

Linux

Windows

Not a real database server, but making use of DLLs

All OS with a Java 7 VM

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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.

Secondary indexes

yes

SQL

Support of SQL

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

yes

but not compliant to any SQL standard

APIs and other access methods

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

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

HTTP API

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC/ADO.Net

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

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

Java Stored Procedures

yes

since Access 2010 using the ACE-engine

Triggers

yes

via the TAP protocol

yes

since Access 2010 using the ACE-engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication between multi datacenters

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Eventual Consistency
Immediate 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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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.

fine grained access rights according to SQL-standard

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

Access rights for users and roles

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.