DBMS > AlaSQL vs. Ignite vs. InfinityDB vs. PlanetScale vs. RocksDB

System Properties Comparison AlaSQL vs. Ignite vs. InfinityDB vs. PlanetScale vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

A Java embedded Key-Value Store which extends the Java Map interface

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Relational DBMS

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial 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	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

Technical documentation

github.com/AlaSQL/alasql

apacheignite.readme.io/docs

boilerbay.com/infinitydb/manual

planetscale.com/docs

github.com/facebook/rocksdb/wiki

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Boiler Bay Inc.

PlanetScale

Facebook, Inc.

Initial release

2014

2015

2002

2020

2013

Current release

Apache Ignite 2.6

4.0

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache 2.0

commercial

Open Source

BSD

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

C++, Java, .Net

Java

C++

Server operating systems

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

Linux
OS X
Solaris
Windows

All OS with a Java VM

Docker
Linux
macOS

Linux

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

schema-free

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

Secondary indexes

yes

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

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

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

APIs and other access methods

JavaScript API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

ADO.NET
JDBC
MySQL protocol
ODBC

C++ API
Java API

Supported programming languages

JavaScript

C#
C++
Java
PHP
Python
Ruby
Scala

Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

proprietary syntax

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes (replicated cache)

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

READ-COMMITTED or SERIALIZED

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

manual creation possible, using inversions based on multi-value capability

yes

not for MyISAM storage engine

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID at shard level

yes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Security Hooks for custom implementations

Users with fine-grained authorization concept

no user groups or roles

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.