DBMS > AlaSQL vs. Apache Druid vs. Percona Server for MongoDB vs. SAP HANA

System Properties Comparison AlaSQL vs. Apache Druid vs. Percona Server for MongoDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store
Relational DBMS

Relational DBMS
Time Series DBMS

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
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	2.85
Rank	#96	Overall
	#50	Relational DBMS
	#6	Time Series DBMS

Score	0.50
Rank	#250	Overall
	#39	Document stores

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

alasql.org

druid.apache.org

www.percona.com/mongodb/software/percona-server-for-mongodb

www.sap.com/products/hana.html

Technical documentation

github.com/AlaSQL/alasql

druid.apache.org/docs/latest/design

docs.percona.com/percona-distribution-for-mongodb

help.sap.com/hana

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation and contributors

Percona

SAP

Initial release

2014

2012

2015

2010

Current release

30.0.0, June 2024

3.4.10-2.10, November 2017

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache license v2

Open Source

GPL Version 2

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

Java

C++

Server operating systems

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

Linux
OS X
Unix

Linux

Appliance or cloud-service

Data scheme

schema-free

yes

schema-less columns are supported

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.

Secondary indexes

yes

SQL

Support of SQL

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

SQL for querying

yes

APIs and other access methods

JavaScript API

JDBC
RESTful HTTP/JSON API

proprietary protocol using JSON

JDBC
ODBC

Supported programming languages

JavaScript

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

JavaScript

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, via HDFS, S3 or other storage engines

Source-replica replication

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

Eventual Consistency
Immediate Consistency

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

Concurrency

Support for concurrent manipulation of data

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

via In-Memory Engine

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users and roles

yes

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.