DBMS > AlaSQL vs. GBase vs. TimesTen vs. Vitess

System Properties Comparison AlaSQL vs. GBase vs. TimesTen vs. Vitess

Please select another system to include it in the comparison.

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.

In-Memory RDBMS compatible to Oracle

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Relational DBMS

Relational DBMS

Secondary database models

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

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

alasql.org

www.gbase.cn

www.oracle.com/database/technologies/related/timesten.html

vitess.io

Technical documentation

github.com/AlaSQL/alasql

docs.oracle.com/database/timesten-18.1

vitess.io/docs

Developer

Andrey Gershun & Mathias R. Wulff

General Data Technology Co., Ltd.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

The Linux Foundation, PlanetScale

Initial release

2014

2004

1998

2013

Current release

GBase 8a, GBase 8s, GBase 8c

11 Release 2 (11.2.2.8.0)

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Apache Version 2.0, commercial licenses available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

C, Java, Python

Server operating systems

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

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

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

with proprietary extensions

APIs and other access methods

JavaScript API

ADO.NET
C API
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

JavaScript

C
C++
Java
PL/SQL

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

PL/SQL

yes

proprietary syntax

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

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 or Eventual Consistency depending on configuration

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

only for local storage and DOM-storage

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

by means of logfiles and checkpoints

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

yes

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Multi faceted data exploration in the browser using Leaflet and amCharts
3 May 2020, Towards Data Science

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Share this page