DBMS > AlaSQL vs. Oracle vs. Valentina Server vs. Vitess

System Properties Comparison AlaSQL vs. Oracle vs. Valentina Server 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

Object-relational database and reports server

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Document store
Spatial DBMS

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	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Score	0.18
Rank	#313	Overall
	#140	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

alasql.org

www.oracle.com/database

www.valentina-db.net

vitess.io

Technical documentation

github.com/AlaSQL/alasql

docs.oracle.com/en/database

valentina-db.com/docs/dokuwiki/v5/doku.php

vitess.io/docs

Developer

Andrey Gershun & Mathias R. Wulff

Oracle

Paradigma Software

The Linux Foundation, PlanetScale

Initial release

2014

1980

1999

2013

Current release

23c, September 2023

5.7.5

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT-License

commercial

restricted free version is available

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

Server operating systems

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

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
OS X
Windows

Docker
Linux
macOS

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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.

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

JavaScript

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

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

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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

isolation level can be parameterized

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

In-memory capabilities

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

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

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.