DBMS > AlaSQL vs. EJDB vs. SAP HANA vs. VelocityDB

System Properties Comparison AlaSQL vs. EJDB vs. SAP HANA vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Graph DBMS
Object oriented 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.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

alasql.org

github.com/Softmotions/ejdb

www.sap.com/products/hana.html

velocitydb.com

Technical documentation

github.com/AlaSQL/alasql

github.com/Softmotions/ejdb/blob/master/README.md

help.sap.com/hana

velocitydb.com/UserGuide

Developer

Andrey Gershun & Mathias R. Wulff

Softmotions

SAP

VelocityDB Inc

Initial release

2014

2012

2010

2011

Current release

2.0 SPS07 (April 4, 2023), April 2023

7.x

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GPLv2

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

Server operating systems

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

server-less

Appliance or cloud-service

Any that supports .NET

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

yes

APIs and other access methods

JavaScript API

in-process shared library

JDBC
ODBC

.Net

Supported programming languages

JavaScript

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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

yes

Based on Windows 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.