DBMS > Axibase vs. GeoSpock vs. Google BigQuery vs. Postgres-XL vs. RDF4J

System Properties Comparison Axibase vs. GeoSpock vs. Google BigQuery vs. Postgres-XL vs. RDF4J

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Spatial and temporal data processing engine for extreme data scale

Large scale data warehouse service with append-only tables

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Time Series DBMS

Relational DBMS

RDF store

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Website

axibase.com/docs/atsd/finance

geospock.com

cloud.google.com/bigquery

www.postgres-xl.org

rdf4j.org

Technical documentation

cloud.google.com/bigquery/docs

www.postgres-xl.org/documentation

rdf4j.org/documentation

Developer

Axibase Corporation

GeoSpock

Google

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2013

2010

2014

since 2012, originally named StormDB

2004

Current release

15585

2.0, September 2019

10 R1, October 2018

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

commercial

Open Source

Mozilla public license

Open Source

Eclipse Distribution License (EDL), v1.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

Java, Javascript

Java

Server operating systems

Linux

hosted

Linux
macOS

Linux
OS X
Unix
Windows

Data scheme

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, 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.

yes

XML type, but no XML query functionality

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

SQL-like query language

ANSI SQL for query only (using Presto)

yes

distributed, parallel query execution

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

JDBC

RESTful HTTP/JSON API

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

Go
Java
PHP
Python
R
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Java
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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.