DBMS > AlaSQL vs. Amazon Redshift vs. Manticore Search vs. Microsoft Azure SQL Database

System Properties Comparison AlaSQL vs. Amazon Redshift vs. Manticore Search vs. Microsoft Azure SQL Database

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

Multi-storage database for search, including full-text search.

Database as a Service offering with high compatibility to Microsoft SQL Server

Primary database model

Document store
Relational DBMS

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS
Spatial DBMS

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

Score	0.49
Rank	#259	Overall
	#40	Document stores
	#120	Relational DBMS

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.23
Rank	#317	Overall
	#21	Search engines

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Website

alasql.org

aws.amazon.com/redshift

manticoresearch.com

azure.microsoft.com/en-us/products/azure-sql/database

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

manual.manticoresearch.com

docs.microsoft.com/en-us/azure/azure-sql

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

Manticore Software

Microsoft

Initial release

2014

2012

2017

2010

Current release

6.0, February 2023

V12

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

GPL version 2

commercial

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

Server operating systems

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

hosted

FreeBSD
Linux
macOS
Windows

hosted

Data scheme

schema-free

yes

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

restricted

yes

full-text index on all search fields

yes

SQL

Support of SQL

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

yes

does not fully support an SQL-standard

SQL-like query language

yes

APIs and other access methods

JavaScript API

JDBC
ODBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET
JDBC
ODBC

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Transact SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Synchronous replication based on Galera library

yes, with always 3 replicas available

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

informational only, not enforced by the system

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

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

The original contents of fields are not stored in the Manticore index.

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

fine grained access rights according to SQL-standard

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.