DBMS > EsgynDB vs. Google Cloud Spanner vs. VoltDB vs. Yanza

System Properties Comparison EsgynDB vs. Google Cloud Spanner vs. VoltDB 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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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.

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Time Series DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.esgyn.cn

cloud.google.com/spanner

www.voltdb.com

yanza.com

Technical documentation

cloud.google.com/spanner/docs

docs.voltdb.com

Developer

Esgyn

Google

VoltDB Inc.

Yanza

Initial release

2015

2017

2010

2015

Current release

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

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++, Java

Java, C++

Server operating systems

Linux

hosted

Linux
OS X

for development

Windows

Data scheme

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
JDBC

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

Java API
JDBC
RESTful HTTP/JSON API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Go
Java
JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

Java Stored Procedures

Java

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication with 3 replicas for regional instances.

Multi-source replication
Source-replica replication

none

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

Foreign keys

Referential integrity

yes

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Strict serializable isolation

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

yes

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

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

Users and roles with access to stored procedures

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Improves Cloud Spanner: More Compute and Storage without Price Increase
14 October 2023, InfoQ.com

Google makes its Cloud Spanner database service faster and more cost-efficient
11 October 2023, SiliconANGLE News

Google turns up the heat on AWS, claims Cloud Spanner is half the cost of DynamoDB
11 October 2023, TechCrunch

Google Cloud just fired a major volley at AWS as the cloud wars heat up
12 October 2023, TechRadar

Google Spanner: When Do You Need to Move to It?
11 September 2023, hackernoon.com

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page