DBMS > AlaSQL vs. Apache Drill vs. Faircom EDGE vs. Snowflake

System Properties Comparison AlaSQL vs. Apache Drill vs. Faircom EDGE vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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

Primary database model

Document store
Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

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

Score	0.49
Rank	#259	Overall
	#40	Document stores
	#120	Relational DBMS

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	0.03
Rank	#380	Overall
	#59	Key-value stores
	#157	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

alasql.org

drill.apache.org

www.faircom.com/products/faircom-edge

www.snowflake.com

Technical documentation

github.com/AlaSQL/alasql

drill.apache.org/docs

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

docs.snowflake.net/manuals/index.html

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

FairCom Corporation

Snowflake Computing Inc.

Initial release

2014

2012

1979

2014

Current release

1.20.3, January 2023

V3, October 2020

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2

commercial

Restricted, free version available

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

ANSI C, C++

Server operating systems

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

Linux
OS X
Windows

Android
Linux

ARM, x86
Raspbian
Windows

hosted

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

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

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

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

SQL SELECT statement is SQL:2003 compliant

yes

ANSI SQL queries

yes

APIs and other access methods

JavaScript API

JDBC
ODBC
RESTful HTTP API

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

JavaScript

C++

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

.Net, JavaScript, C/C++

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

File partitioning

Customizable business rules for partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Synchronous and asynchronous realtime replication based on transaction logs

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
Tunable Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

Depending on the underlying data source

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 user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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.