DBMS > Cubrid vs. Google Cloud Datastore vs. HEAVY.AI vs. JSqlDb

System Properties Comparison Cubrid vs. Google Cloud Datastore vs. HEAVY.AI vs. JSqlDb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

JavaScript Query Language Database, stores JavaScript objects and primitives

Primary database model

Relational DBMS

Document store

Relational DBMS

Document store
Object oriented DBMS

Secondary database models

Spatial DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Website

cubrid.com (korean)
cubrid.org (english)

cloud.google.com/datastore

github.com/heavyai/heavydb
www.heavy.ai

jsqldb.org (offline)

Technical documentation

cubrid.org/manuals

cloud.google.com/datastore/docs

docs.heavy.ai

Developer

CUBRID Corporation, CUBRID Foundation

Google

HEAVY.AI, Inc.

Konrad von Backstrom

Initial release

2008

2016

2018

Current release

11.0, January 2021

5.10, January 2022

0.8, December 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

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.

Implementation language

C, C++, Java

C++ and CUDA

Server operating systems

Linux
Windows

hosted

Linux

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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 (GQL)

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

Supported programming languages

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

Server-side scripts

Stored procedures

Java Stored Procedures

using Google App Engine

functions in JavaScript

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication using Paxos

Multi-source 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

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using RocksDB

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)

fine grained access rights according to SQL-standard

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 Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
29 April 2024, TechRadar

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Big Data Analytics: A Game Changer for Infrastructure
13 July 2023, Spiceworks News and Insights

HEAVY.AI Launches HEAVY 7.0, Introducing Real-Time Machine Learning Capabilities
19 April 2023, businesswire.com

Making the most of geospatial intelligence
14 April 2023, InfoWorld

HEAVY.AI Partners with Bain, Maxar, and Nvidia to Provide Digital Twins for Telecom Networks
16 February 2023, Datanami

The insideBIGDATA IMPACT 50 List for Q4 2023
11 October 2023, insideBIGDATA

provided by Google News

Share this page