DBMS > GeoSpock vs. Google BigQuery vs. NSDb vs. WakandaDB

System Properties Comparison GeoSpock vs. Google BigQuery vs. NSDb vs. WakandaDB

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

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Time Series DBMS

Object oriented DBMS

Secondary database models

Time Series DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

geospock.com

cloud.google.com/bigquery

nsdb.io

wakanda.github.io

Technical documentation

cloud.google.com/bigquery/docs

nsdb.io/Architecture

wakanda.github.io/doc

Developer

GeoSpock

Google

Wakanda SAS

Initial release

2010

2017

2012

Current release

2.0, September 2019

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

AGPLv3, extended commercial license 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

Java, Javascript

Java, Scala

C++, JavaScript

Server operating systems

hosted

Linux
macOS

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like query language

APIs and other access methods

JDBC

RESTful HTTP/JSON API

gRPC
HTTP REST
WebSocket

RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
Scala

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

none

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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)

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.