DBMS > AlaSQL vs. Apache IoTDB vs. EJDB vs. EsgynDB

System Properties Comparison AlaSQL vs. Apache IoTDB vs. EJDB vs. EsgynDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

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

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

Primary database model

Document store
Relational DBMS

Time Series DBMS

Document store

Relational 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	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Website

alasql.org

iotdb.apache.org

github.com/Softmotions/ejdb

www.esgyn.cn

Technical documentation

github.com/AlaSQL/alasql

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

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

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Softmotions

Esgyn

Initial release

2014

2018

2012

2015

Current release

1.1.0, April 2023

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2.0

Open Source

GPLv2

commercial

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

Server operating systems

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

All OS with a Java VM (>= 1.8)

server-less

Linux

Data scheme

schema-free

yes

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.

SQL-like query language

yes

APIs and other access methods

JavaScript API

JDBC
Native API

in-process shared library

ADO.NET
JDBC
ODBC

Supported programming languages

JavaScript

C
C#
C++
Go
Java
Python
Scala

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

none

Sharding

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

none

Multi-source replication between multi datacenters

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Strong Consistency with Raft

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

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

AMD EPYC 4364P & 4564P @ DDR5-4800 / DDR5-5200 vs. Intel Xeon E-2488 Review
6 June 2024, Phoronix

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

Linux 6.5 With AMD P-State EPP Default Brings Performance & Power Efficiency Benefits For Ryzen Servers
21 September 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

AMD EPYC 8324P / 8324PN Siena 32-Core Siena Linux Server Performance Review
10 October 2023, Phoronix

provided by Google News

Share this page