DBMS > GeoSpock vs. Lovefield vs. OpenQM vs. TimescaleDB

System Properties Comparison GeoSpock vs. Lovefield vs. OpenQM vs. TimescaleDB

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

Embeddable relational database for web apps written in pure JavaScript

QpenQM is a high-performance, self-tuning, multi-value DBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Multivalue DBMS

Time Series DBMS

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

geospock.com

google.github.io/lovefield

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.timescale.com

Technical documentation

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

docs.timescale.com

Developer

GeoSpock

Google

Rocket Software, originally Martin Phillips

Timescale

Initial release

2014

1993

2017

Current release

2.0, September 2019

2.1.12, February 2017

3.4-12

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPLv2, extended commercial license available

Open Source

Apache 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.

Implementation language

Java, Javascript

JavaScript

Server operating systems

hosted

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

tested with Chrome, Firefox, IE, Safari

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

full PostgreSQL SQL syntax

APIs and other access methods

JDBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

JavaScript

.Net
Basic
C
Java
Objective C
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

yes

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication with hot standby and reads on replicas

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

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

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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

Recent citations in the news

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

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

Imagining an 'Everything Connected' World With Geospock | AWS Startups Blog
20 June 2019, AWS Blog

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

GeoSpock launches pioneering new spatial Big Data platform
27 February 2019, Geospatial World

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, Microsoft

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

TimescaleDB goes distributed; implements ‘Chunking’ over ‘Sharding’ for scaling-out
22 August 2019, Packt Hub

provided by Google News

Share this page