DBMS > GeoSpock vs. Google BigQuery vs. Hive vs. Informix

System Properties Comparison GeoSpock vs. Google BigQuery vs. Hive vs. Informix

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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

A secure embeddable database from IBM, positioned besides IBM Db2 as a relatively low-cost product optimized for OLTP and Internet of Things data

Primary database model

Relational DBMS

Since Version 12.10 support for JSON/BSON datatypes compatible with MongoDB

Secondary database models

Time Series DBMS

Document store
Spatial DBMS
Time Series DBMS

with Informix TimeSeries Extension

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	17.87
Rank	#35	Overall
	#22	Relational DBMS

Website

geospock.com

cloud.google.com/bigquery

hive.apache.org

www.ibm.com/products/informix

Technical documentation

cloud.google.com/bigquery/docs

cwiki.apache.org/confluence/display/Hive/Home

informix.hcldoc.com
www.ibm.com/support/knowledgecenter/SSGU8G/welcomeIfxServers.html

Developer

GeoSpock

Google

Apache Software Foundation

initially developed by Facebook

IBM, HCL Technologies

Effective May 1st, 2017, HCL took on development, technical support, and product management teams, and works jointly with IBM on product strategy, marketing, and sales.

Initial release

2010

2012

1984

Current release

2.0, September 2019

3.1.3, April 2022

14.10.FC5, November 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

free developer edition 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

C, C++ and Java

Server operating systems

hosted

All OS with a Java VM

AIX
HP-UX
Linux
macOS
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

Since Version 12.10 support for JSON/BSON datatypes

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

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC

RESTful HTTP/JSON API

JDBC
ODBC
Thrift

JDBC
JSON API

MongoDB compatible
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
PHP
Python

.Net
C
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions and integration of map-reduce

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

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)

Access rights for users, groups and roles

Users with fine-grained authentication, authorization, and auditing controls

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.