DBMS > AlaSQL vs. Ehcache vs. EsgynDB vs. Riak TS

System Properties Comparison AlaSQL vs. Ehcache vs. EsgynDB vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

A widely adopted Java cache with tiered storage options

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Document store
Relational DBMS

Key-value store

Relational DBMS

Time Series 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	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

alasql.org

www.ehcache.org

www.esgyn.cn

Technical documentation

github.com/AlaSQL/alasql

www.ehcache.org/documentation

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Andrey Gershun & Mathias R. Wulff

Terracotta Inc, owned by Software AG

Esgyn

Open Source, formerly Basho Technologies

Initial release

2014

2009

2015

Current release

3.10.0, March 2022

3.0.0, September 2022

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

JavaScript

Java

C++, Java

Erlang

Server operating systems

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

All OS with a Java VM

Linux

Linux
OS X

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

yes

restricted

SQL

Support of SQL

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

yes

yes, limited

APIs and other access methods

JavaScript API

JCache

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

JavaScript

Java

All languages supporting JDBC/ODBC/ADO.Net

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

by using Terracotta Server

Multi-source replication between multi datacenters

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

yes

only for local storage and DOM-storage

yes

supports JTA and can work as an XA resource

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

using a tiered cache-storage approach

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

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

provided by Google News

Scaling Australia's Most Popular Online News Sites with Ehcache
6 December 2010, InfoQ.com

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, dzone.com

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

provided by Google News

Share this page