DBMS > AlaSQL vs. CrateDB vs. Google BigQuery vs. TimescaleDB

System Properties Comparison AlaSQL vs. CrateDB vs. Google BigQuery vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Distributed Database based on Lucene

Large scale data warehouse service with append-only tables

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Document store
Relational DBMS

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Relational 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	0.71
Rank	#227	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#10	Vector DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

alasql.org

cratedb.com

cloud.google.com/bigquery

www.timescale.com

Technical documentation

github.com/AlaSQL/alasql

cratedb.com/docs

cloud.google.com/bigquery/docs

docs.timescale.com

Developer

Andrey Gershun & Mathias R. Wulff

Crate

Google

Timescale

Initial release

2014

2013

2010

2017

Current release

2.15.0, May 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

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

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

hosted

Linux
OS X
Windows

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL

Support of SQL

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

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

full PostgreSQL SQL syntax

APIs and other access methods

JavaScript API

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

JavaScript

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions (Javascript)

user defined functions

in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Configurable replication on table/partition-level

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Read-after-write consistency on record level

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

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

User concepts

Access control

rights management via user accounts

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.