DBMS > Amazon SimpleDB vs. Apache Impala vs. Elasticsearch vs. Google BigQuery

System Properties Comparison Amazon SimpleDB vs. Apache Impala vs. Elasticsearch vs. Google BigQuery

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted simple database service by Amazon, with the data stored in the Amazon Cloud.

There is an unrelated product called SimpleDB developed by Edward Sciore

Analytic DBMS for Hadoop

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

Large scale data warehouse service with append-only tables

Primary database model

Secondary database models

Document store

Document store
Spatial DBMS
Vector DBMS

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

Score	1.85
Rank	#138	Overall
	#24	Key-value stores

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

aws.amazon.com/simpledb

impala.apache.org

www.elastic.co/elasticsearch

cloud.google.com/bigquery

Technical documentation

docs.aws.amazon.com/simpledb

impala.apache.org/impala-docs.html

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

cloud.google.com/bigquery/docs

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Elastic

Google

Initial release

2007

2013

2010

Current release

4.1.0, June 2022

8.6, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Elastic License

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

C++

Java

Server operating systems

hosted

Linux

All OS with a Java VM

hosted

Data scheme

schema-free

yes

schema-free

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

yes

Typing

predefined data types such as float or date

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 columns are indexed automatically

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

Supported programming languages

.Net
C
C++
Erlang
Java
PHP
Python
Ruby
Scala

All languages supporting JDBC/ODBC

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

user defined functions

in JavaScript

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

none

Sharding must be implemented in the application

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Concurrent data updates can be detected by the application

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

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.

Memcached and Redis integration

User concepts

Access control

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & 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.