DBMS > GeoMesa vs. Google BigQuery vs. STSdb vs. VoltDB

System Properties Comparison GeoMesa vs. Google BigQuery vs. STSdb vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Large scale data warehouse service with append-only tables

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.geomesa.org

cloud.google.com/bigquery

github.com/STSSoft/STSdb4

www.voltdb.com

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

cloud.google.com/bigquery/docs

docs.voltdb.com

Developer

CCRi and others

Google

STS Soft SC

VoltDB Inc.

Initial release

2014

2010

2011

2010

Current release

5.0.0, May 2024

4.0.8, September 2015

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPLv2, commercial license available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Scala

Java, C++

Server operating systems

hosted

Windows

Linux
OS X

for development

Data scheme

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP/JSON API

.NET Client API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

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

Google Cloud Identity & Access Management (IAM)

Users and roles with access to stored procedures

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.