DBMS > AlaSQL vs. Geode vs. Google BigQuery vs. Tarantool vs. XTDB

System Properties Comparison AlaSQL vs. Geode vs. Google BigQuery vs. Tarantool vs. XTDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Large scale data warehouse service with append-only tables

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Relational DBMS

Key-value store

Relational DBMS

Document store
Key-value store
Relational DBMS

Document store

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

alasql.org

geode.apache.org

cloud.google.com/bigquery

www.tarantool.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

github.com/AlaSQL/alasql

geode.apache.org/docs

cloud.google.com/bigquery/docs

www.tarantool.io/en/doc

www.xtdb.com/docs

Developer

Andrey Gershun & Mathias R. Wulff

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Google

Juxt Ltd.

Initial release

2014

2002

2010

2008

2019

Current release

1.1, February 2017

2.10.0, May 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

MIT License

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

C and C++

Clojure

Server operating systems

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

All OS with a Java VM

the JDK (8 or later) is also required

hosted

BSD
Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

schema-free

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

yes, extensible-data-notation format

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.

SQL-like query language (OQL)

yes

Full-featured ANSI SQL support

limited SQL, making use of Apache Calcite

APIs and other access methods

JavaScript API

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

Open binary protocol

HTTP REST
JDBC

Supported programming languages

JavaScript

.Net
All JVM based languages
C++
Groovy
Java
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Lua, C and SQL stored procedures

Triggers

yes

Cache Event Listeners

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

yes, on a single node

Since BigQuery is designed for querying data

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

yes, write ahead logging

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights per client and object definable

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

Google Cloud Identity & Access Management (IAM)

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.