DBMS > AlaSQL vs. Amazon Redshift vs. GeoMesa vs. JanusGraph vs. JSqlDb

System Properties Comparison AlaSQL vs. Amazon Redshift vs. GeoMesa vs. JanusGraph vs. JSqlDb

Editorial information provided by DB-Engines

Name

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

JavaScript Query Language Database, stores JavaScript objects and primitives

Primary database model

Document store
Relational DBMS

Relational DBMS

Spatial DBMS

Graph DBMS

Document store
Object oriented DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Website

alasql.org

aws.amazon.com/redshift

www.geomesa.org

janusgraph.org

jsqldb.org (offline)

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

www.geomesa.org/documentation/stable/user/index.html

docs.janusgraph.org

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

CCRi and others

Linux Foundation; originally developed as Titan by Aurelius

Konrad von Backstrom

Initial release

2014

2012

2014

2017

2018

Current release

5.0.0, May 2024

0.6.3, February 2023

0.8, December 2018

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

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

Scala

Java

Server operating systems

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

hosted

Linux
OS X
Unix
Windows

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

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

restricted

yes

SQL

Support of SQL

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

yes

does not fully support an SQL-standard

APIs and other access methods

JavaScript API

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

Clojure
Java
Python

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

yes

functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

depending on storage layer

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

depending on storage layer

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

depending on storage layer

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graphs

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

using RocksDB

In-memory capabilities

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

yes

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

User authentification and security via Rexster Graph Server

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.