DBMS > Google Cloud Spanner vs. MySQL vs. OpenSearch vs. Transwarp Hippo

System Properties Comparison Google Cloud Spanner vs. MySQL vs. OpenSearch vs. Transwarp Hippo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Widely used open source RDBMS

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

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

Relational DBMS

Key/Value like access via memcached API

Search engine

Vector DBMS

Secondary database models

Document store
Spatial DBMS

Vector DBMS

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

Score	2.69
Rank	#101	Overall
	#51	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	16.31
Rank	#36	Overall
	#4	Search engines

Score	0.00
Rank	#385	Overall
	#16	Vector DBMS

Website

cloud.google.com/spanner

www.mysql.com

github.com/opensearch-project
opensearch.org

www.transwarp.cn/en/subproduct/hippo

Technical documentation

cloud.google.com/spanner/docs

dev.mysql.com/doc

opensearch.org/docs/latest

Developer

Google

Oracle

since 2010, originally MySQL AB, then Sun

Amazon Web Services

Initial release

2017

1995

2021

2023

Current release

9.0.0, July 2024

2.5.0, January 2023

1.0, May 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

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.

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

C and C++

Java

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
macOS

Data scheme

yes

schema-free

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

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

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

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

Go
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

C++
Java
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication with 3 replicas for regional instances.

Multi-source replication
Source-replica replication

yes

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

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

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Strict serializable isolation

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

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

Users with fine-grained authorization concept

no user groups or roles

Role based access control and fine grained access rights

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.