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

System Properties Comparison Databricks vs. EsgynDB vs. Google Cloud Bigtable vs. Hyprcubd 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

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

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

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	81.08
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

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

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.databricks.com

www.esgyn.cn

cloud.google.com/bigtable

hyprcubd.com (offline)

www.sap.com/products/hana.html

Technical documentation

docs.databricks.com

cloud.google.com/bigtable/docs

help.sap.com/hana

Developer

Databricks

Esgyn

Google

Hyprcubd, Inc.

SAP

Initial release

2013

2015

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

hosted

Linux

hosted

Appliance or cloud-service

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

with Databricks SQL

yes

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

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

gRPC (https)

JDBC
ODBC

Supported programming languages

Python
R
Scala

All languages supporting JDBC/ODBC/ADO.Net

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

Server-side scripts

Stored procedures

user defined functions and aggregates

Java Stored Procedures

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

yes

Multi-source replication between multi datacenters

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

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

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

yes

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» 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.