DBMS > BigchainDB vs. Google Cloud Datastore vs. HyperSQL vs. OpenSearch

System Properties Comparison BigchainDB vs. Google Cloud Datastore vs. HyperSQL vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

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

Primary database model

Document store

Relational DBMS

Search engine

Secondary database models

Vector DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	3.23
Rank	#93	Overall
	#48	Relational DBMS

Score	16.03
Rank	#37	Overall
	#4	Search engines

Website

www.bigchaindb.com

cloud.google.com/datastore

hsqldb.org

github.com/opensearch-project
opensearch.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

cloud.google.com/datastore/docs

hsqldb.org/web/hsqlDocsFrame.html

opensearch.org/docs/latest

Developer

Google

Amazon Web Services

Initial release

2016

2008

2001

2021

Current release

2.7.2, June 2023

2.5.0, January 2023

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

based on BSD license

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

Python

Java

Server operating systems

Linux

hosted

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

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, details here

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

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

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

HTTP API

JDBC via HTTP
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

All languages supporting JDBC/ODBC
Java

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

using Google App Engine

Java, SQL

yes

Triggers

Callbacks using the Google Apps Engine

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

none

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

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

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

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,with MongoDB ord RethinkDB

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

yes

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

fine grained access rights according to SQL-standard

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.