DBMS > GeoSpock vs. JaguarDB vs. OpenSearch vs. PlanetScale

System Properties Comparison GeoSpock vs. JaguarDB vs. OpenSearch vs. PlanetScale

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

Performant, highly scalable DBMS for AI and IoT applications

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

Vector DBMS

Document store
Spatial DBMS

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

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#15	Vector DBMS

Score	16.03
Rank	#37	Overall
	#4	Search engines

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

geospock.com

www.jaguardb.com

github.com/opensearch-project
opensearch.org

planetscale.com

Technical documentation

www.jaguardb.com/support.html

opensearch.org/docs/latest

planetscale.com/docs

Developer

GeoSpock

DataJaguar, Inc.

Amazon Web Services

PlanetScale

Initial release

2015

2021

2020

Current release

2.0, September 2019

3.3 July 2023

2.5.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

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.
STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.

Implementation language

Java, Javascript

C++

the server part. Clients available in other languages

Java

Server operating systems

hosted

Linux

All OS with a Java VM

Docker
Linux
macOS

Data scheme

yes

schema-free

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

yes

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)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC

JDBC
ODBC

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 for users can be defined per table

rights management via user accounts

Users with fine-grained authorization concept

no user groups or 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.