DBMS > AlaSQL vs. Drizzle vs. Ingres vs. Microsoft Azure Cosmos DB vs. Prometheus

System Properties Comparison AlaSQL vs. Drizzle vs. Ingres vs. Microsoft Azure Cosmos DB vs. Prometheus

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

JavaScript DBMS library

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

Well established RDBMS

Globally distributed, horizontally scalable, multi-model database service

Open-source Time Series DBMS and monitoring system

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

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

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

alasql.org

www.actian.com/databases/ingres

azure.microsoft.com/services/cosmos-db

prometheus.io

Technical documentation

github.com/AlaSQL/alasql

docs.actian.com/ingres

learn.microsoft.com/azure/cosmos-db

prometheus.io/docs

Developer

Andrey Gershun & Mathias R. Wulff

Drizzle project, originally started by Brian Aker

Actian Corporation

Microsoft

Initial release

2014

2008

1974

originally developed at University Berkely in early 1970s

2014

2015

Current release

7.2.4, September 2012

11.2, May 2022

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GNU GPL

commercial

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

JavaScript

C++

Server operating systems

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

FreeBSD
Linux
OS X

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

Numeric data only

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.

but tools for importing/exporting data from/to XML-files available

Import of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

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

yes

with proprietary extensions

yes

SQL-like query language

APIs and other access methods

JavaScript API

JDBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP/JSON API

Supported programming languages

JavaScript

C
C++
Java
PHP

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

hooks for callbacks inside the server can be used.

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Ingres Replicator

yes

Implicit feature of the cloud service

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.