DBMS > Amazon CloudSearch vs. Atos Standard Common Repository vs. Elasticsearch vs. SQLite

System Properties Comparison Amazon CloudSearch vs. Atos Standard Common Repository vs. Elasticsearch vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Widely used embeddable, in-process RDBMS

Primary database model

Search engine

Document store
Key-value store

Search engine

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	1.87
Rank	#140	Overall
	#12	Search engines

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/cloudsearch

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.elastic.co/elasticsearch

www.sqlite.org

Technical documentation

docs.aws.amazon.com/cloudsearch

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

www.sqlite.org/docs.html

Developer

Amazon

Atos Convergence Creators

Elastic

Dwayne Richard Hipp

Initial release

2012

2016

2010

2000

Current release

1703

8.6, January 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Elastic License

Open Source

Public Domain

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

Java

Server operating systems

hosted

Linux

All OS with a Java VM

server-less

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

dynamic column types

Typing

predefined data types such as float or date

yes

optional

yes

not rigid because of 'dynamic typing' concept.

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 search fields are automatically indexed

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API

LDAP

Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages with LDAP bindings

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Memcached and Redis integration

yes

User concepts

Access control

authentication via encrypted signatures

LDAP bind authentication

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.