DBMS > AlaSQL vs. Apache Drill vs. Graph Engine vs. Postgres-XL vs. Snowflake

System Properties Comparison AlaSQL vs. Apache Drill vs. Graph Engine vs. Postgres-XL vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

Document store
Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Document store
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	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

drill.apache.org/docs

www.graphengine.io/docs/manual

www.postgres-xl.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Microsoft

Snowflake Computing Inc.

Initial release

2014

2012

2010

2014

since 2012, originally named StormDB

2014

Current release

1.20.3, January 2023

10 R1, October 2018

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2

Open Source

MIT License

Open Source

Mozilla public license

commercial

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

.NET and C

Server operating systems

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

Linux
OS X
Windows

.NET

Linux
macOS

hosted

Data scheme

schema-free

yes

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

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

XML type, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

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

SQL SELECT statement is SQL:2003 compliant

yes

distributed, parallel query execution

yes

APIs and other access methods

JavaScript API

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

CLI Client
JDBC
ODBC

Supported programming languages

JavaScript

C++

C#
C++
F#
Visual Basic

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

Depending on the underlying data source

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

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

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.