DBMS > Amazon CloudSearch vs. IRONdb vs. Spark SQL vs. SQLite vs. Vitess

System Properties Comparison Amazon CloudSearch vs. IRONdb vs. Spark SQL vs. SQLite vs. Vitess

Editorial information provided by DB-Engines

Name

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

Description

A hosted search engine 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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Search engine

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

aws.amazon.com/cloudsearch

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

spark.apache.org/sql

www.sqlite.org

vitess.io

Technical documentation

docs.aws.amazon.com/cloudsearch

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

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

vitess.io/docs

Developer

Amazon

Circonus LLC.

Apache Software Foundation

Dwayne Richard Hipp

The Linux Foundation, PlanetScale

Initial release

2012

2017

2014

2000

2013

Current release

V0.10.20, January 2018

3.5.0 ( 2.13), September 2023

3.46.0 (23 May 2024), May 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

Apache Version 2.0, commercial licenses available

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

C and C++

Scala

Server operating systems

hosted

Linux

Linux
OS X
Windows

server-less

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

all search fields are automatically indexed

yes

SQL

Support of SQL

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

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

yes

with proprietary extensions

APIs and other access methods

HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

Java
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

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

yes, in Lua

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Automatic, metric affinity per node

yes, utilizing Spark Core

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

configurable replication factor, datacenter aware

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

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

authentication via encrypted signatures

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.