DBMS > AlaSQL vs. GBase vs. Google BigQuery vs. Splunk vs. XTDB

System Properties Comparison AlaSQL vs. GBase vs. Google BigQuery vs. Splunk vs. XTDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

Large scale data warehouse service with append-only tables

Analytics Platform for Big Data

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Search engine

Document store

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	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

alasql.org

www.gbase.cn

cloud.google.com/bigquery

www.splunk.com

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

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/bigquery/docs

docs.splunk.com/Documentation/Splunk

www.xtdb.com/docs

Developer

Andrey Gershun & Mathias R. Wulff

General Data Technology Co., Ltd.

Google

Splunk Inc.

Juxt Ltd.

Initial release

2014

2004

2010

2003

2019

Current release

GBase 8a, GBase 8s, GBase 8c

1.19, September 2021

License

Commercial or Open Source

Open Source

MIT-License

commercial

Limited free edition and free developer edition available

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

C, Java, Python

Clojure

Server operating systems

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

Linux

hosted

Linux
OS X
Solaris
Windows

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

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

Standard with numerous extensions

yes

Splunk Search Processing Language for search commands

limited SQL, making use of Apache Calcite

APIs and other access methods

JavaScript API

ADO.NET
C API
JDBC
ODBC

RESTful HTTP/JSON API

HTTP REST

HTTP REST
JDBC

Supported programming languages

JavaScript

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by range, list and hash) and vertical partitioning

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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

ACID

Since BigQuery is designed for querying data

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

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

User concepts

Access control

yes

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

Google Cloud Identity & Access Management (IAM)

Access rights for 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.