DBMS > CockroachDB vs. Google Cloud Datastore vs. SAP HANA vs. SQream DB

System Properties Comparison CockroachDB vs. Google Cloud Datastore vs. SAP HANA vs. SQream DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

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

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Document store

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	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

www.cockroachlabs.com

cloud.google.com/datastore

www.sap.com/products/hana.html

sqream.com

Technical documentation

www.cockroachlabs.com/docs

cloud.google.com/datastore/docs

help.sap.com/hana

docs.sqream.com

Developer

Cockroach Labs

Google

SAP

SQream Technologies

Initial release

2015

2008

2010

2017

Current release

24.1.0, May 2024

2.0 SPS07 (April 4, 2023), April 2023

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

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++, CUDA, Haskell, Java, Scala

Server operating systems

Linux
macOS
Windows

hosted

Appliance or cloud-service

Linux

Data scheme

dynamic schema

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

yes, ANSI Standard SQL Types

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, wire compatible with PostgreSQL

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC

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

JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

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

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

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

using Google App Engine

SQLScript, R

user defined functions in Python

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication using Paxos

yes

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

yes

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

In-memory capabilities

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

yes

User concepts

Access control

Role-based access control

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

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.