DBMS > Alibaba Cloud Table Store vs. GridDB vs. Heroic vs. OpenSearch

System Properties Comparison Alibaba Cloud Table Store vs. GridDB vs. Heroic vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

Scalable in-memory time series database optimized for IoT and Big Data

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Primary database model

Wide column store

Time Series DBMS

Search engine

Secondary database models

Key-value store
Relational DBMS

Vector DBMS

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

Score	0.24
Rank	#310	Overall
	#12	Wide column stores

Score	2.02
Rank	#132	Overall
	#11	Time Series DBMS

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	15.65
Rank	#38	Overall
	#4	Search engines

Website

www.alibabacloud.com/product/table-store

griddb.net

github.com/spotify/heroic

github.com/opensearch-project
opensearch.org

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.griddb.net

spotify.github.io/heroic

opensearch.org/docs/latest

Developer

Alibaba

Toshiba Corporation

Spotify

Amazon Web Services

Initial release

2016

2013

2014

2021

Current release

5.1, August 2022

2.5.0, January 2023

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Apache 2.0

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.

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

Java

Server operating systems

hosted

Linux

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

numerical, string, blob, geometry, boolean, timestamp

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

via Elasticsearch

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

APIs and other access methods

HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

Java
Python

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

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

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic single-row operations

ACID at container level

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 based on subaccounts and tokens

Access rights for users can be defined per database

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

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

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

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

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

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

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.