DBMS > GeoSpock vs. Lovefield vs. PostGIS vs. TerarkDB vs. VoltDB

System Properties Comparison GeoSpock vs. Lovefield vs. PostGIS vs. TerarkDB vs. VoltDB

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

Embeddable relational database for web apps written in pure JavaScript

Spatial extension of PostgreSQL

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

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

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

geospock.com

google.github.io/lovefield

postgis.net

github.com/bytedance/terarkdb

www.voltdb.com

Technical documentation

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

postgis.net/documentation

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.voltdb.com

Developer

GeoSpock

Google

ByteDance, originally Terark

VoltDB Inc.

Initial release

2014

2005

2016

2010

Current release

2.0, September 2019

2.1.12, February 2017

3.4.2, February 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL v2.0

commercial

restricted open source version available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, Javascript

JavaScript

C++

Java, C++

Server operating systems

hosted

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

tested with Chrome, Firefox, IE, Safari

Linux
OS X

for development

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.

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

via JavaScript builder pattern

yes

only a subset of SQL 99

APIs and other access methods

JDBC

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

JavaScript

C++
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Java

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

yes

based on PostgreSQL

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

none

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

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

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

yes

Snapshots and command logging

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

Access rights for users can be defined per table

yes

based on PostgreSQL

Users and roles with access to stored procedures

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

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

nChain leads investment round in extreme-scale data firm GeoSpock
2 October 2020, CoinGeek

GeoSpock’s extreme-scale data mission in $5.4m funding boost
8 October 2020, Cambridge Independent

Big data processing techniques to streamline analytics
5 October 2018, TechTarget

The most promising deep tech startups of Cambridge in 2021
10 May 2021, UKTN (UK Technology News

provided by Google News

A Chinese company is making the cloud 200x faster · TechNode
3 July 2017, TechNode

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page