DBMS > AlaSQL vs. MySQL vs. Teradata vs. YottaDB

System Properties Comparison AlaSQL vs. MySQL vs. Teradata vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Widely used open source RDBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

A fast and solid embedded Key-value store

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Relational DBMS

using the Octo plugin

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.42
Rank	#264	Overall
	#42	Document stores
	#122	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Score	0.21
Rank	#309	Overall
	#43	Key-value stores

Website

Technical documentation

github.com/AlaSQL/alasql

dev.mysql.com/doc

docs.teradata.com

yottadb.com/resources/documentation

Developer

Andrey Gershun & Mathias R. Wulff

Oracle

since 2010, originally MySQL AB, then Sun

Teradata

YottaDB, LLC

Initial release

2014

1995

1984

2001

Current release

9.0.0, July 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

AGPL 3.0

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

Server operating systems

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

FreeBSD
Linux
OS X
Solaris
Windows

hosted
Linux

Docker
Linux

Data scheme

schema-free

yes

schema-free

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

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

yes

with proprietary extensions

yes

SQL 2016 + extensions

by using the Octo plugin

APIs and other access methods

JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

JavaScript

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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

not for MyISAM storage engine

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Users and groups based on OS-security mechanisms

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.