DBMS > Databricks vs. Google Cloud Datastore vs. Hawkular Metrics vs. RocksDB vs. STSdb

System Properties Comparison Databricks vs. Google Cloud Datastore vs. Hawkular Metrics vs. RocksDB vs. STSdb

Editorial information provided by DB-Engines

Name

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.

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

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Relational DBMS

Document store

Time Series DBMS

Key-value store

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

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.databricks.com

cloud.google.com/datastore

www.hawkular.org

rocksdb.org

github.com/STSSoft/STSdb4

Technical documentation

docs.databricks.com

cloud.google.com/datastore/docs

www.hawkular.org/hawkular-metrics/docs/user-guide

github.com/facebook/rocksdb/wiki

Developer

Databricks

Google

Community supported by Red Hat

Facebook, Inc.

STS Soft SC

Initial release

2013

2008

2014

2013

2011

Current release

8.11.4, April 2024

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

Open Source

GPLv2, commercial license available

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

Java

C++

Server operating systems

hosted

Linux
OS X
Windows

Linux

Windows

Data scheme

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

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

yes

primitive types and user defined types (classes)

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

SQL-like query language (GQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

HTTP REST

C++ API
Java API

.NET Client API

Supported programming languages

Python
R
Scala

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

Go
Java
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

user defined functions and aggregates

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

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.

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

yes

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

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

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.