DBMS > Adabas vs. AlaSQL vs. Drizzle vs. Google Cloud Datastore vs. SQLite

System Properties Comparison Adabas vs. AlaSQL vs. Drizzle vs. Google Cloud Datastore vs. SQLite

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

used typically together with the Natural programming platform

JavaScript DBMS library

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Widely used embeddable, in-process RDBMS

Primary database model

Multivalue DBMS

Document store
Relational DBMS

Relational DBMS

Document store

Relational DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

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

alasql.org

cloud.google.com/datastore

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/datastore/docs

www.sqlite.org/docs.html

Developer

Software AG

Andrey Gershun & Mathias R. Wulff

Drizzle project, originally started by Brian Aker

Google

Dwayne Richard Hipp

Initial release

1971

2014

2008

2000

Current release

7.2.4, September 2012

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

MIT-License

Open Source

GNU GPL

commercial

Open Source

Public Domain

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

JavaScript

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

server-less, requires a JavaScript environment (browser, Node.js)

FreeBSD
Linux
OS X

hosted

server-less

Data scheme

yes

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes, details here

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

with proprietary extensions

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

JavaScript API

JDBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Natural

JavaScript

C
C++
Java
PHP

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

in Natural

using Google App Engine

Triggers

yes

hooks for callbacks inside the server can be used.

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

none

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

yes

only for local storage and DOM-storage

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.