DBMS > GeoSpock vs. Lovefield vs. PouchDB vs. SAP HANA vs. TerarkDB

System Properties Comparison GeoSpock vs. Lovefield vs. PouchDB vs. SAP HANA vs. TerarkDB

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

JavaScript DBMS with an API inspired by CouchDB

In-memory, column based data store. Available as appliance or cloud service

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

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

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

Website

geospock.com

google.github.io/lovefield

pouchdb.com

www.sap.com/products/hana.html

github.com/bytedance/terarkdb

Technical documentation

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

pouchdb.com/guides

help.sap.com/hana

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

GeoSpock

Google

Apache Software Foundation

SAP

ByteDance, originally Terark

Initial release

2014

2012

2010

2016

Current release

2.0, September 2019

2.1.12, February 2017

7.1.1, June 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Javascript

JavaScript

C++

Server operating systems

hosted

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

tested with Chrome, Firefox, IE, Safari

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

Appliance or cloud-service

Data scheme

yes

schema-free

yes

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

via views

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

JDBC

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC

C++ API
Java API

Supported programming languages

JavaScript

C++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

SQLScript, R

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

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

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

by using IndexedDB, WebSQL or LevelDB as backend

yes

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

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.