DBMS > AlaSQL vs. Amazon Redshift vs. PlanetScale vs. Quasardb

System Properties Comparison AlaSQL vs. Amazon Redshift vs. PlanetScale vs. Quasardb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

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

Distributed, high-performance timeseries database

Primary database model

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial 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	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

alasql.org

aws.amazon.com/redshift

planetscale.com

quasar.ai

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

planetscale.com/docs

doc.quasar.ai/master

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

PlanetScale

quasardb

Initial release

2014

2012

2020

2009

Current release

3.14.1, January 2024

License

Commercial or Open Source

Open Source

MIT-License

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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++

Server operating systems

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

hosted

Docker
Linux
macOS

BSD
Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

restricted

yes

with tags

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

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JavaScript API

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP API

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

ACID at shard level

ACID

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

by using LevelDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Cryptographically strong user authentication and audit trail

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.