DBMS > GeoSpock vs. OpenSearch vs. Percona Server for MongoDB vs. TerarkDB

System Properties Comparison GeoSpock vs. OpenSearch vs. Percona Server for MongoDB vs. TerarkDB

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 distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Time Series DBMS

Vector DBMS

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

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	0.52
Rank	#254	Overall
	#39	Document stores

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

Website

geospock.com

github.com/opensearch-project
opensearch.org

www.percona.com/mongodb/software/percona-server-for-mongodb

github.com/bytedance/terarkdb

Technical documentation

opensearch.org/docs/latest

docs.percona.com/percona-distribution-for-mongodb

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

GeoSpock

Amazon Web Services

Percona

ByteDance, originally Terark

Initial release

2021

2015

2016

Current release

2.0, September 2019

2.5.0, January 2023

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPL Version 2

commercial

restricted open source version available

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

Java

C++

Server operating systems

hosted

All OS with a Java VM

Linux

Data scheme

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

temporal, categorical

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

APIs and other access methods

JDBC

Java API
RESTful HTTP/JSON API

proprietary protocol using JSON

C++ API
Java API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C++
Java

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

via In-Memory Engine

yes

User concepts

Access control

Access rights for users can be defined per table

Access rights for users and roles

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.