DBMS > Adabas vs. searchxml vs. Snowflake vs. Tigris vs. TinkerGraph

System Properties Comparison Adabas vs. searchxml vs. Snowflake vs. Tigris vs. TinkerGraph

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

DBMS for structured and unstructured content wrapped with an application server

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

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Multivalue DBMS

Native XML DBMS
Search engine

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Graph DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

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

www.searchxml.net/category/products

www.snowflake.com

www.tigrisdata.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

www.tigrisdata.com/docs

Developer

Software AG

informationpartners gmbh

Snowflake Computing Inc.

Tigris Data, Inc.

Initial release

1971

2015

2014

2022

2009

Current release

1.0

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Windows

hosted

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

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

yes

schema-free

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

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

CLI Client
gRPC
RESTful HTTP API

TinkerPop 3

Supported programming languages

Natural

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)

Groovy
Java

Server-side scripts

Stored procedures

in Natural

yes

on the application server

user defined functions

Triggers

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

sychronisation to multiple collections

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

optional

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)

Domain, group and role-based access control at the document level and for application services

Users with fine-grained authorization concept, user roles and pluggable authentication

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.