DBMS > Amazon CloudSearch vs. Google Cloud Datastore vs. OpenSearch vs. Tarantool

System Properties Comparison Amazon CloudSearch vs. Google Cloud Datastore vs. OpenSearch vs. Tarantool

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Search engine

Document store

Search engine

Document store
Key-value store
Relational DBMS

Secondary database models

Vector DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

aws.amazon.com/cloudsearch

cloud.google.com/datastore

github.com/opensearch-project
opensearch.org

www.tarantool.io

Technical documentation

docs.aws.amazon.com/cloudsearch

cloud.google.com/datastore/docs

opensearch.org/docs/latest

www.tarantool.io/en/doc

Developer

Amazon

Google

Amazon Web Services

Initial release

2012

2008

2021

2008

Current release

2.5.0, January 2023

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.
STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.

Implementation language

Java

C and C++

Server operating systems

hosted

All OS with a Java VM

BSD
Linux
macOS

Data scheme

yes

schema-free

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

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

yes, details here

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

Open binary protocol

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

using Google App Engine

yes

Lua, C and SQL stored procedures

Triggers

Callbacks using the Google Apps Engine

yes

by using the 'percolation' feature

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication using Paxos

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

authentication via encrypted signatures

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.