DBMS > Geode vs. Microsoft Azure AI Search vs. OpenSearch vs. Teradata Aster

System Properties Comparison Geode vs. Microsoft Azure AI Search vs. OpenSearch vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Search-as-a-service for web and mobile app development

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

Platform for big data analytics on multistructured data sources and types

Primary database model

Key-value store

Search engine

Relational DBMS

Secondary database models

Vector DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

geode.apache.org

azure.microsoft.com/en-us/services/search

github.com/opensearch-project
opensearch.org

Technical documentation

geode.apache.org/docs

learn.microsoft.com/en-us/azure/search

opensearch.org/docs/latest

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

Amazon Web Services

Teradata

Initial release

2002

2015

2021

2005

Current release

1.1, February 2017

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

Apache Version 2.0

commercial

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

All OS with a Java VM

the JDK (8 or later) is also required

hosted

All OS with a Java VM

Linux

Data scheme

schema-free

yes

schema-free

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

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

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.

yes

in Aster File Store

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP API

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
Java
JavaScript
Python

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

yes

R packages

Triggers

yes

Cache Event Listeners

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

Multi-source replication

yes

Implicit feature of the cloud service

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

ACID

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 per client and object definable

yes

using Azure authentication

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.