DBMS > AlaSQL vs. JaguarDB vs. Microsoft Azure Cosmos DB vs. SAP SQL Anywhere vs. ToroDB

System Properties Comparison AlaSQL vs. JaguarDB vs. Microsoft Azure Cosmos DB vs. SAP SQL Anywhere vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

JavaScript DBMS library

Performant, highly scalable DBMS for AI and IoT applications

Globally distributed, horizontally scalable, multi-model database service

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store
Relational DBMS

Key-value store
Vector DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

alasql.org

www.jaguardb.com

azure.microsoft.com/services/cosmos-db

www.sap.com/products/technology-platform/sql-anywhere.html

github.com/torodb/server

Technical documentation

github.com/AlaSQL/alasql

www.jaguardb.com/support.html

learn.microsoft.com/azure/cosmos-db

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Andrey Gershun & Mathias R. Wulff

DataJaguar, Inc.

Microsoft

SAP

formerly Sybase

8Kdata

Initial release

2014

2015

2014

1992

2016

Current release

3.3 July 2023

17, July 2015

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GPL V3.0

commercial

Open Source

AGPL-V3

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

the server part. Clients available in other languages

Java

Server operating systems

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

Linux

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

string, integer, double, boolean, date, object_id

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

All properties auto-indexed by default

yes

SQL

Support of SQL

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

yes

APIs and other access methods

JavaScript API

JDBC
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

JavaScript

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

yes, in C/C++, Java, .Net or Perl

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

Implicit feature of the cloud service

Source-replica replication

Database mirroring

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Eventual Consistency
Immediate 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

Multi-item ACID transactions with snapshot isolation within a partition

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

In-memory capabilities

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

yes

User concepts

Access control

rights management via user accounts

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.