DBMS > Google Cloud Datastore vs. HEAVY.AI vs. STSdb vs. XTDB

System Properties Comparison Google Cloud Datastore vs. HEAVY.AI vs. STSdb vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Spatial DBMS

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

cloud.google.com/datastore

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

github.com/STSSoft/STSdb4

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

cloud.google.com/datastore/docs

docs.heavy.ai

www.xtdb.com/docs

Developer

Google

HEAVY.AI, Inc.

STS Soft SC

Juxt Ltd.

Initial release

2008

2016

2011

2019

Current release

5.10, January 2022

4.0.8, September 2015

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

GPLv2, commercial license available

Open Source

MIT License

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++ and CUDA

Clojure

Server operating systems

hosted

Linux

Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

yes

primitive types and user defined types (classes)

yes, extensible-data-notation format

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

SQL-like query language (GQL)

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

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

JDBC
ODBC
Thrift
Vega

.NET Client API

HTTP REST
JDBC

Supported programming languages

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

All languages supporting JDBC/ODBC/Thrift
Python

C#
Java

Clojure
Java

Server-side scripts

Stored procedures

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Multi-source replication

none

yes, each node contains all data

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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)

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 vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
13 September 2024, TechRadar

What Is Google Cloud? Platform, Benefits & More Explained
11 September 2024, Cloudwards

Google App Engine
26 April 2024, TechTarget

provided by Google News

5 Q’s for Mike Flaxman, Vice President of Heavy.AI
15 August 2024, Center for Data Innovation

Dr. Mike Flaxman, VP or Product Management at HEAVY.AI – Interview Series
19 September 2024, Unite.AI

HEAVY.AI Accelerates Big Data Analytics with Vultr's High-Performance GPU Cloud Infrastructure
11 September 2024, insideBIGDATA

HEAVY.AI Accelerates Big Data Analytics with Vultr’s High-Performance GPU Cloud Infrastructure
11 September 2024, insideBIGDATA

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

provided by Google News

Share this page