DBMS > Google Cloud Spanner vs. MySQL vs. Vertica vs. Yanza

System Properties Comparison Google Cloud Spanner vs. MySQL vs. Vertica vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Column oriented

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS
Time Series 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	9.62
Rank	#42	Overall
	#26	Relational DBMS

Website

cloud.google.com/spanner

www.mysql.com

www.vertica.com

yanza.com

Technical documentation

cloud.google.com/spanner/docs

dev.mysql.com/doc

vertica.com/documentation

Developer

Google

Oracle

since 2010, originally MySQL AB, then Sun

OpenText

previously Micro Focus and Hewlett Packard

Yanza

Initial release

2017

1995

2005

2015

Current release

9.0.0, July 2024

12.0.3, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Limited community edition free

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Windows

Data scheme

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

schema-free

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.

yes

Secondary indexes

yes

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

yes

with proprietary extensions

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

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

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

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

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

proprietary syntax

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

yes, called Custom Alerts

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning, hierarchical partitioning

none

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

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

Transaction concepts

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

ACID

Strict serializable isolation

ACID

not for MyISAM storage engine

ACID

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

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

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.