DBMS > AlaSQL vs. Google BigQuery vs. KeyDB vs. Rockset

System Properties Comparison AlaSQL vs. Google BigQuery vs. KeyDB vs. Rockset

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 with append-only tables

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Document store

Secondary database models

Relational DBMS
Search engine

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.42
Rank	#264	Overall
	#42	Document stores
	#122	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	1.07
Rank	#180	Overall
	#31	Document stores

Website

alasql.org

cloud.google.com/bigquery

github.com/Snapchat/KeyDB
keydb.dev

rockset.com

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/bigquery/docs

docs.keydb.dev

docs.rockset.com

Developer

Andrey Gershun & Mathias R. Wulff

Google

EQ Alpha Technology Ltd.

Rockset

Initial release

2014

2010

2019

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

BSD-3

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

C++

Server operating systems

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

hosted

Linux

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

by using the Redis Search module

all fields are automatically indexed

SQL

Support of SQL

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

yes

Read-only SQL queries, including JOINs

APIs and other access methods

JavaScript API

RESTful HTTP/JSON API

Proprietary protocol

RESP - REdis Serialization Protoco

HTTP REST

Supported programming languages

JavaScript

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Eventual 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

Since BigQuery is designed for querying data

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

simple password-based access control and ACL

Access rights for users and organizations can be defined via Rockset console

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.