DBMS > GeoSpock vs. HEAVY.AI vs. Lovefield vs. OpenSearch

System Properties Comparison GeoSpock vs. HEAVY.AI vs. Lovefield vs. OpenSearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

Primary database model

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

Spatial DBMS

Vector DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Website

geospock.com

github.com/heavyai/heavydb
www.heavy.ai

google.github.io/lovefield

github.com/opensearch-project
opensearch.org

Technical documentation

docs.heavy.ai

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

opensearch.org/docs/latest

Developer

GeoSpock

HEAVY.AI, Inc.

Google

Amazon Web Services

Initial release

2016

2014

2021

Current release

2.0, September 2019

5.10, January 2022

2.1.12, February 2017

2.5.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition 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

Java, Javascript

C++ and CUDA

JavaScript

Java

Server operating systems

hosted

Linux

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

tested with Chrome, Firefox, IE, Safari

All OS with a Java VM

Data scheme

yes

schema-free

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

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

temporal, categorical

yes

All search fields are automatically indexed

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like query language

via JavaScript builder pattern

SQL-like query language

APIs and other access methods

JDBC

JDBC
ODBC
Thrift
Vega

Java API
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

yes

Triggers

Using read-only observers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

Round robin

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Transaction concepts

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

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

User concepts

Access control

Access rights for users can be defined per table

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.