DBMS > AlaSQL vs. Google BigQuery vs. IRONdb vs. Realm vs. STSdb

System Properties Comparison AlaSQL vs. Google BigQuery vs. IRONdb vs. Realm vs. STSdb

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

JavaScript DBMS library

Large scale data warehouse service with append-only tables

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Relational 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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

alasql.org

cloud.google.com/bigquery

www.circonus.com/solutions/time-series-database/

realm.io

github.com/STSSoft/STSdb4

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/bigquery/docs

docs.circonus.com/irondb/category/getting-started

realm.io/docs

Developer

Andrey Gershun & Mathias R. Wulff

Google

Circonus LLC.

Realm, acquired by MongoDB in May 2019

STS Soft SC

Initial release

2014

2010

2017

2014

2011

Current release

V0.10.20, January 2018

4.0.8, September 2015

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

GPLv2, commercial license available

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

Server operating systems

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

hosted

Linux

Android
Backend: server-less
iOS
Windows

Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

primitive types and user defined types (classes)

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.

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

JavaScript API

RESTful HTTP/JSON API

HTTP API

.NET Client API

Supported programming languages

JavaScript

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.Net
Java

with Android only
Objective-C
React Native
Swift

C#
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes, in Lua

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

configurable replication factor, datacenter aware

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate 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

ACID

Concurrency

Support for concurrent manipulation of data

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

In-Memory realm

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

yes

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.