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

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

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

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

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Secondary database models

Vector DBMS

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

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.04
Rank	#374	Overall
	#38	Time Series DBMS

Score	15.65
Rank	#38	Overall
	#4	Search engines

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

Website

cloud.google.com/datastore

www.hawkular.org

github.com/opensearch-project
opensearch.org

github.com/STSSoft/STSdb4

Technical documentation

cloud.google.com/datastore/docs

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

opensearch.org/docs/latest

Developer

Google

Community supported by Red Hat

Amazon Web Services

STS Soft SC

Initial release

2008

2014

2021

2011

Current release

2.5.0, January 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Java

Server operating systems

hosted

Linux
OS X
Windows

All OS with a Java VM

Windows

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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.

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

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

HTTP REST

Java API
RESTful HTTP/JSON API

.NET Client API

Supported programming languages

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

Go
Java
Python
Ruby

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

C#
Java

Server-side scripts

Stored procedures

using Google App Engine

yes

Triggers

Callbacks using the Google Apps Engine

yes

via Hawkular Alerting

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

In-memory capabilities

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

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

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» 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.