DBMS > AlaSQL vs. Apache IoTDB vs. Ehcache vs. GeoSpock vs. SQLite

System Properties Comparison AlaSQL vs. Apache IoTDB vs. Ehcache vs. GeoSpock vs. SQLite

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

JavaScript DBMS library

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

A widely adopted Java cache with tiered storage options

Spatial and temporal data processing engine for extreme data scale

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Time Series DBMS

Key-value store

Relational DBMS

Secondary database models

Time Series 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	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

geospock.com

Technical documentation

github.com/AlaSQL/alasql

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

www.ehcache.org/documentation

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Terracotta Inc, owned by Software AG

GeoSpock

Dwayne Richard Hipp

Initial release

2014

2018

2009

2000

Current release

1.1.0, April 2023

3.10.0, March 2022

2.0, September 2019

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Public Domain

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

Java

Java, Javascript

Server operating systems

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

All OS with a Java VM (>= 1.8)

All OS with a Java VM

hosted

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

temporal, categorical

yes

SQL

Support of SQL

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

SQL-like query language

ANSI SQL for query only (using Presto)

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

JDBC
Native API

JCache

JDBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

C
C#
C++
Go
Java
Python
Scala

Java

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

by using Terracotta Server

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

yes

by using Terracotta Server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Strong Consistency with Raft

Tunable Consistency (Strong, Eventual, Weak)

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

yes

Access rights for users can be defined per table

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.