DBMS > Adabas vs. Dragonfly vs. mSQL vs. Snowflake

System Properties Comparison Adabas vs. Dragonfly vs. mSQL 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

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

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.79
Rank	#102	Overall
	#2	Multivalue DBMS

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

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

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

hughestech.com.au/products/msql

www.snowflake.com

Technical documentation

www.dragonflydb.io/docs

docs.snowflake.net/manuals/index.html

Developer

Software AG

DragonflyDB team and community contributors

Hughes Technologies

Snowflake Computing Inc.

Initial release

1971

2023

1994

2014

Current release

1.0, March 2023

4.4, October 2021

License

Commercial or Open Source

commercial

Open Source

BSL 1.1

commercial

free licenses can be provided

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

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

hosted

Data scheme

yes

scheme-free

yes

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

Typing

predefined data types such as float or date

yes

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

yes

with add-on product Adabas SQL Gateway

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

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

RESP - REdis Serialization Protocol

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Natural

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++
Delphi
Java
Perl
PHP
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in Natural

Lua

user defined functions

Triggers

publish/subscribe channels provide some trigger functionality

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

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

Immediate Consistency

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

Durability

Support for making data persistent

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

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

Password-based authentication

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.