DBMS > Bangdb vs. Google Cloud Datastore vs. Hyprcubd vs. OpenSearch

System Properties Comparison Bangdb vs. Google Cloud Datastore vs. Hyprcubd vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

Converged and high performance database for device data, events, time series, document and graph

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

Serverless Time Series DBMS

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

Primary database model

Document store
Graph DBMS
Time Series DBMS

Document store

Time Series DBMS

Search engine

Secondary database models

Spatial DBMS

Vector DBMS

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

Score	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

bangdb.com

cloud.google.com/datastore

hyprcubd.com (offline)

github.com/opensearch-project
opensearch.org

Technical documentation

docs.bangdb.com

cloud.google.com/datastore/docs

opensearch.org/docs/latest

Developer

Sachin Sinha, BangDB

Google

Hyprcubd, Inc.

Amazon Web Services

Initial release

2012

2008

2021

Current release

BangDB 2.0, October 2021

2.5.0, January 2023

License

Commercial or Open Source

Open Source

BSD 3

commercial

Open Source

Apache Version 2.0

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.

STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.
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

C, C++

Java

Server operating systems

Linux

hosted

All OS with a Java VM

Data scheme

schema-free

yes

schema-free

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

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

yes, details here

yes

time, int, uint, float, string

yes

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

secondary, composite, nested, reverse, geospatial

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL like support with command line tool

SQL-like query language (GQL)

SQL-like query language

APIs and other access methods

Proprietary protocol
RESTful HTTP API

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

gRPC (https)

Java API
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Java
Python

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

using Google App Engine

yes

Triggers

yes, Notifications (with Streaming only)

Callbacks using the Google Apps Engine

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Multi-source replication using Paxos

yes

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

Tunable consistency, set CAP knob accordingly

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

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, optimistic concurrency control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

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

yes, run db with in-memory only mode

User concepts

Access control

yes (enterprise version only)

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

token access

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.