DBMS > Adabas vs. Microsoft Azure Table Storage vs. Oracle vs. SiteWhere

System Properties Comparison Adabas vs. Microsoft Azure Table Storage vs. Oracle vs. SiteWhere

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 Wide Column Store for rapid development using massive semi-structured datasets

Widely used RDBMS

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

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

azure.microsoft.com/en-us/services/storage/tables

www.oracle.com/database

github.com/sitewhere/sitewhere

Technical documentation

docs.oracle.com/en/database

sitewhere1.sitewhere.io/index.html

Developer

Software AG

Microsoft

Oracle

SiteWhere

Initial release

1971

2012

1980

2010

Current release

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.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 and C++

Java

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Schemaless in JSON and XML columns

predefined scheme

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

with proprietary extensions

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST

Supported programming languages

Natural

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

in Natural

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

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

optimistic locking

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

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

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.