DBMS > GeoMesa vs. GeoSpock vs. Lovefield vs. TerarkDB vs. Vitess

System Properties Comparison GeoMesa vs. GeoSpock vs. Lovefield vs. TerarkDB vs. Vitess

Editorial information provided by DB-Engines

Name

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

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Spatial and temporal data processing engine for extreme data scale

Embeddable relational database for web apps written in pure JavaScript

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.geomesa.org

geospock.com

google.github.io/lovefield

github.com/bytedance/terarkdb

vitess.io

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

vitess.io/docs

Developer

CCRi and others

GeoSpock

Google

ByteDance, originally Terark

The Linux Foundation, PlanetScale

Initial release

2014

2016

2013

Current release

5.0.0, May 2024

2.0, September 2019

2.1.12, February 2017

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

commercial

restricted open source version available

Open Source

Apache Version 2.0, commercial licenses 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.

Implementation language

Scala

Java, Javascript

JavaScript

C++

Server operating systems

hosted

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

tested with Chrome, Firefox, IE, Safari

Docker
Linux
macOS

Data scheme

yes

schema-free

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

yes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

via JavaScript builder pattern

yes

with proprietary extensions

APIs and other access methods

JDBC

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

JavaScript

C++
Java

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

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Automatic sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

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

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

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.

depending on storage layer

yes

using MemoryDB

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users can be defined per table

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

GeoSpock launches Spatial Big Data Platform 2.0
4 September 2019, VanillaPlus

Cambridge-based data analytics startup GeoSpock lands €4.6 million
2 October 2020, EU-Startups

nChain Leads Investment Round in Extreme-scale Data Firm GeoSpock
2 October 2020, AlexaBlockchain

Smart Cities, Autonomous Vehicles, Artificial General Intelligence Robotics: Q&A with Steve Marsh, GeoSpock
16 May 2018, ExchangeWire

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

provided by Google News

Share this page