DBMS > AlaSQL vs. Amazon Redshift vs. BoltDB vs. GeoMesa vs. Hazelcast

System Properties Comparison AlaSQL vs. Amazon Redshift vs. BoltDB vs. GeoMesa vs. Hazelcast

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

An embedded key-value store for Go.

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

A widely adopted in-memory data grid

Primary database model

Document store
Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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.80
Rank	#215	Overall
	#31	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Website

alasql.org

aws.amazon.com/redshift

github.com/boltdb/bolt

www.geomesa.org

hazelcast.com

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

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

hazelcast.org/imdg/docs

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

CCRi and others

Hazelcast

Initial release

2014

2012

2013

2014

2008

Current release

5.0.0, May 2024

5.3.6, November 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

MIT License

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses 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

Scala

Java

Server operating systems

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

hosted

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Data scheme

schema-free

yes

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.

yes

the object must implement a serialization strategy

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

SQL-like query language

APIs and other access methods

JavaScript API

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Event Listeners, Executor Services

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

depending on storage layer

yes

Replicated Map

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

none

depending on storage layer

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

yes

one or two-phase-commit; repeatable reads; read commited

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

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Role-based access control

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.