DBMS > AlaSQL vs. Amazon Redshift vs. Google Cloud Spanner vs. IBM Cloudant vs. jBASE

System Properties Comparison AlaSQL vs. Amazon Redshift vs. Google Cloud Spanner vs. IBM Cloudant vs. jBASE

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Database as a Service offering based on Apache CouchDB

A robust multi-value DBMS comprising development tools and middleware

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

Multivalue 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	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Website

alasql.org

aws.amazon.com/redshift

cloud.google.com/spanner

www.ibm.com/products/cloudant

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

cloud.google.com/spanner/docs

cloud.ibm.com/docs/Cloudant

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Rocket Software (formerly Zumasys)

Initial release

2014

2012

2017

2010

1991

Current release

5.7

License

Commercial or Open Source

Open Source

MIT-License

commercial

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

Erlang

Server operating systems

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

hosted

AIX
Linux
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

restricted

yes

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

Query statements complying to ANSI 2011

Embedded SQL for jBASE in BASIC

APIs and other access methods

JavaScript API

JDBC
ODBC

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
Basic
Jabbascript
Java

Server-side scripts

Stored procedures

user defined functions

in Python

View functions (Map-Reduce) in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication with 3 replicas for regional instances.

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Strict serializable isolation

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic 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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users can be defined per database

Access rights can be defined down to the item level

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.