DBMS > EsgynDB vs. Google Cloud Bigtable vs. Hyprcubd vs. PlanetScale vs. SAP HANA

System Properties Comparison EsgynDB vs. Google Cloud Bigtable vs. Hyprcubd vs. PlanetScale vs. SAP HANA

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Serverless Time Series DBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.esgyn.cn

cloud.google.com/bigtable

hyprcubd.com (offline)

planetscale.com

www.sap.com/products/hana.html

Technical documentation

cloud.google.com/bigtable/docs

planetscale.com/docs

help.sap.com/hana

Developer

Esgyn

Google

Hyprcubd, Inc.

PlanetScale

SAP

Initial release

2015

2020

2010

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++, Java

Server operating systems

Linux

hosted

Docker
Linux
macOS

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

gRPC (https)

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

Atomic single-row operations

ACID at shard level

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

fine grained access rights according to SQL-standard

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

token access

Users with fine-grained authorization concept

no user groups or roles

yes

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.