DBMS > Adabas vs. Memcached vs. Microsoft Access vs. Snowflake

System Properties Comparison Adabas vs. Memcached vs. Microsoft Access vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

In-memory key-value store, originally intended for caching

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

Multivalue DBMS

Key-value store

Relational DBMS

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

Score	2.64
Rank	#104	Overall
	#1	Multivalue DBMS

Score	16.84
Rank	#32	Overall
	#4	Key-value stores

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

www.softwareag.com/en_corporate/platform/adabas-natural.html

www.memcached.org

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

www.snowflake.com

Technical documentation

github.com/memcached/memcached/wiki

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

Software AG

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Snowflake Computing Inc.

Initial release

1971

2003

1992

2014

Current release

1.6.29, June 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

BSD license

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

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

FreeBSD
Linux
OS X
Unix
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

yes

schema-free

yes

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

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

yes

with add-on product Adabas SQL Gateway

yes

but not compliant to any SQL standard

yes

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

Proprietary protocol

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

Natural

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in Natural

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

none

Repcached, a Memcached patch, provides this functionallity

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

yes

using SASL (Simple Authentication and Security Layer) protocol

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.