DBMS > AlaSQL vs. Amazon CloudSearch vs. Amazon DynamoDB vs. IRONdb vs. Manticore Search

System Properties Comparison AlaSQL vs. Amazon CloudSearch vs. Amazon DynamoDB vs. IRONdb vs. Manticore Search

Editorial information provided by DB-Engines

Name

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

Description

JavaScript DBMS library

A hosted search engine service by Amazon with the data stored in Amazons cloud

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Primary database model

Document store
Relational DBMS

Search engine

Document store
Key-value store

Time Series DBMS

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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	1.81
Rank	#137	Overall
	#12	Search engines

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.29
Rank	#302	Overall
	#21	Search engines

Website

alasql.org

aws.amazon.com/cloudsearch

aws.amazon.com/dynamodb

www.circonus.com/solutions/time-series-database/

manticoresearch.com

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/cloudsearch

docs.aws.amazon.com/dynamodb

docs.circonus.com/irondb/category/getting-started

manual.manticoresearch.com

Developer

Andrey Gershun & Mathias R. Wulff

Amazon

Circonus LLC.

Manticore Software

Initial release

2014

2012

2017

Current release

V0.10.20, January 2018

6.0, February 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

free tier for a limited amount of database operations

commercial

Open Source

GPL version 2

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

C++

Server operating systems

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

hosted

Linux

FreeBSD
Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

Fixed schema

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

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

Secondary indexes

yes

all search fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

APIs and other access methods

JavaScript API

HTTP API

RESTful HTTP API

HTTP API

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

Supported programming languages

JavaScript

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Server-side scripts

Stored procedures

yes, in Lua

user defined functions

Triggers

yes

by integration with AWS Lambda

Partitioning methods

Methods for storing different data on different nodes

none

yes

automatic partitioning across Amazon Search Instance as required

Sharding

Automatic, metric affinity per node

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

managed transparently by AWS

yes

configurable replication factor, datacenter aware

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate consistency per node, eventual consistency across nodes

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

ACID

ACID across one or more tables within a single AWS account and region

yes

isolated transactions for atomic changes and binary logging for safe writes

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.

In-memory capabilities

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

yes

User concepts

Access control

authentication via encrypted signatures

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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.