DBMS > Geode vs. Lovefield vs. OpenSearch vs. Tkrzw

System Properties Comparison Geode vs. Lovefield vs. OpenSearch vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Embeddable relational database for web apps written in pure JavaScript

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

geode.apache.org

google.github.io/lovefield

github.com/opensearch-project
opensearch.org

dbmx.net/tkrzw

Technical documentation

geode.apache.org/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

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.

Google

Amazon Web Services

Mikio Hirabayashi

Initial release

2002

2014

2021

2020

Current release

1.1, February 2017

2.1.12, February 2017

2.5.0, January 2023

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

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

JavaScript

Java

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

All OS with a Java VM

Linux
macOS

Data scheme

schema-free

yes

schema-free

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

schema-free

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.

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language

via JavaScript builder pattern

SQL-like query language

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Java API
RESTful HTTP/JSON API

Supported programming languages

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

JavaScript

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Cache Event Listeners

Using read-only observers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

using specific database classes

User concepts

Access control

Access rights per client and object definable

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.