DBMS > GeoSpock vs. Google BigQuery vs. LevelDB vs. Postgres-XL

System Properties Comparison GeoSpock vs. Google BigQuery vs. LevelDB vs. Postgres-XL

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

Large scale data warehouse service with append-only tables

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	2.75
Rank	#107	Overall
	#19	Key-value stores

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Website

geospock.com

cloud.google.com/bigquery

github.com/google/leveldb

www.postgres-xl.org

Technical documentation

cloud.google.com/bigquery/docs

github.com/google/leveldb/blob/main/doc/index.md

www.postgres-xl.org/documentation

Developer

GeoSpock

Google

Initial release

2010

2011

2014

since 2012, originally named StormDB

Current release

2.0, September 2019

1.23, February 2021

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

Mozilla public license

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

C++

Server operating systems

hosted

Illumos
Linux
OS X
Windows

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.

yes

XML type, but no XML query functionality

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

distributed, parallel query execution

APIs and other access methods

JDBC

RESTful HTTP/JSON API

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

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

Since BigQuery is designed for querying data

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

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

User concepts

Access control

Access rights for users can be defined per table

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.