DBMS > Datomic vs. Google Cloud Datastore vs. Hawkular Metrics vs. STSdb

System Properties Comparison Datomic vs. Google Cloud Datastore vs. Hawkular Metrics vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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.

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

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

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.04
Rank	#374	Overall
	#38	Time Series DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

www.datomic.com

cloud.google.com/datastore

www.hawkular.org

github.com/STSSoft/STSdb4

Technical documentation

docs.datomic.com

cloud.google.com/datastore/docs

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

Developer

Cognitect

Google

Community supported by Red Hat

STS Soft SC

Initial release

2012

2008

2014

2011

Current release

1.0.6735, June 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

All OS with a Java VM

hosted

Linux
OS X
Windows

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (GQL)

APIs and other access methods

RESTful HTTP API

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

HTTP REST

.NET Client API

Supported programming languages

Clojure
Java

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

Go
Java
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

yes

Transaction Functions

using Google App Engine

Triggers

By using transaction functions

Callbacks using the Google Apps Engine

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

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

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

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Zoona Case Study
16 December 2017, AWS Blog

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Relational, NoSQL, Ledger Databases work, not Permissioned Blockchains.
13 January 2019, hackernoon.com

provided by Google News

Google Cloud is NOT magicking away data egress fees
12 January 2024, The Stack

SAP adds vector datastore to HANA Cloud database
2 November 2023, Techzine Europe

NetApp Cloud Volumes Service datastore support for Google Cloud VMware Engine
7 February 2023, NetApp

Your Memories. Their Cloud.
1 January 2023, The New York Times

All of Google’s cloud database services are now out of beta
16 August 2016, TechCrunch

provided by Google News

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

Share this page