DBMS > Adabas vs. JanusGraph vs. Snowflake vs. Sqrrl vs. Tarantool

System Properties Comparison Adabas vs. JanusGraph vs. Snowflake vs. Sqrrl vs. Tarantool

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

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

used typically together with the Natural programming platform

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

Adaptable, secure NoSQL built on Apache Accumulo

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Multivalue DBMS

Graph DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

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

janusgraph.org

www.snowflake.com

sqrrl.com

www.tarantool.io

Technical documentation

docs.janusgraph.org

docs.snowflake.net/manuals/index.html

www.tarantool.io/en/doc

Developer

Software AG

Linux Foundation; originally developed as Titan by Aurelius

Snowflake Computing Inc.

Amazon

originally Sqrrl Data, Inc.

Initial release

1971

2017

2014

2012

2008

Current release

0.6.3, February 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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

Java

C and C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Unix
Windows

hosted

Linux

BSD
Linux
macOS

Data scheme

yes

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

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

CLI Client
JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Open binary protocol

Supported programming languages

Natural

Clojure
Java
Python

JavaScript (Node.js)
Python

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

in Natural

yes

user defined functions

Lua, C and SQL stored procedures

Triggers

yes

similar concept for controling cloud resources

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

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

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

yes

Sharding

making use of Hadoop

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

selectable replication factor

making use of Hadoop

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

yes, write ahead logging

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

User authentification and security via Rexster Graph Server

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.