DBMS > Amazon CloudSearch vs. Google BigQuery vs. Solr vs. Warp 10

System Properties Comparison Amazon CloudSearch vs. Google BigQuery vs. Solr vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

A widely used distributed, scalable search engine based on Apache Lucene

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Spatial DBMS

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

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/cloudsearch

cloud.google.com/bigquery

solr.apache.org

www.warp10.io

Technical documentation

docs.aws.amazon.com/cloudsearch

cloud.google.com/bigquery/docs

solr.apache.org/resources.html

www.warp10.io/content/02_Getting_started

Developer

Amazon

Google

Apache Software Foundation

SenX

Initial release

2012

2010

2006

2015

Current release

9.6.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache License 2.0

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

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux
OS X
Windows

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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.

yes

Secondary indexes

yes

all search fields are automatically indexed

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

HTTP API

RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java plugins

yes

WarpScript

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

optimistic locking

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.

yes

User concepts

Access control

authentication via encrypted signatures

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

Google Cloud Identity & Access Management (IAM)

yes

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.