DBMS > Adabas vs. EsgynDB vs. RDF4J vs. Snowflake

System Properties Comparison Adabas vs. EsgynDB vs. RDF4J 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

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

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

Score	3.58
Rank	#91	Overall
	#1	Multivalue DBMS

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

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

www.esgyn.cn

rdf4j.org

www.snowflake.com

Technical documentation

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Software AG

Esgyn

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

Initial release

1971

2015

2004

2014

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

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++, Java

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux

Linux
OS X
Unix
Windows

hosted

Data scheme

yes

RDF Schemas

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

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

ADO.NET
JDBC
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Supported programming languages

Natural

All languages supporting JDBC/ODBC/ADO.Net

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in Natural

Java Stored Procedures

yes

user defined functions

Triggers

yes

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

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication between multi datacenters

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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)

fine grained access rights according to SQL-standard

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.