DBMS > AlaSQL vs. Apache Impala vs. Dgraph vs. Google Cloud Firestore vs. MySQL

System Properties Comparison AlaSQL vs. Apache Impala vs. Dgraph vs. Google Cloud Firestore vs. MySQL

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Analytic DBMS for Hadoop

Distributed and scalable native Graph DBMS

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Widely used open source RDBMS

Primary database model

Document store
Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	0.42
Rank	#264	Overall
	#42	Document stores
	#122	Relational DBMS

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	1.39
Rank	#155	Overall
	#15	Graph DBMS

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

alasql.org

impala.apache.org

dgraph.io

firebase.google.com/products/firestore

www.mysql.com

Technical documentation

github.com/AlaSQL/alasql

impala.apache.org/impala-docs.html

dgraph.io/docs

firebase.google.com/docs/firestore

dev.mysql.com/doc

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Dgraph Labs, Inc.

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2013

2016

2017

1995

Current release

4.1.0, June 2022

9.0.0, July 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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++

C and C++

Server operating systems

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

Linux

Linux
OS X
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

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

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

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC
ODBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

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

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes, Firebase Rules & Cloud Functions

yes

proprietary syntax

Triggers

yes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Synchronous replication via Raft

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Planned for future releases

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Users with fine-grained authorization concept

no user groups or roles

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.