DBMS > GeoSpock vs. Google BigQuery vs. Stardog vs. Trafodion

System Properties Comparison GeoSpock vs. Google BigQuery vs. Stardog vs. Trafodion

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.

Apache Trafodion has been retired in 2021. Therefore it is 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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

geospock.com

cloud.google.com/bigquery

www.stardog.com

trafodion.apache.org

Technical documentation

cloud.google.com/bigquery/docs

docs.stardog.com

trafodion.apache.org/documentation.html

Developer

GeoSpock

Google

Stardog-Union

Apache Software Foundation, originally developed by HP

Initial release

2010

2014

Current release

2.0, September 2019

7.3.0, May 2020

2.3.0, February 2019

License

Commercial or Open Source

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

Apache 2.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, Javascript

Java

C++, Java

Server operating systems

hosted

Linux
macOS
Windows

Linux

Data scheme

yes

schema-free and OWL/RDFS-schema support

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.

Import/export of XML data possible

Secondary indexes

temporal, categorical

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

yes

APIs and other access methods

JDBC

RESTful HTTP/JSON API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions and aggregates, HTTP Server extensions in Java

Java Stored Procedures

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in HA-Cluster

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

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 and roles

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.