DBMS > GeoMesa vs. gStore vs. Spark SQL vs. Transbase vs. VoltDB

System Properties Comparison GeoMesa vs. gStore vs. Spark SQL vs. Transbase vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

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

A native Graph DBMS to store and maintain very large RDF datasets.

Spark SQL is a component on top of 'Spark Core' for structured data processing

A resource-optimized, high-performance, universally applicable RDBMS

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

Spatial DBMS

Graph DBMS
RDF store

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.14
Rank	#342	Overall
	#34	Graph DBMS
	#16	RDF stores

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.geomesa.org

en.gstore.cn

spark.apache.org/sql

www.transaction.de/en/products/transbase.html

www.voltdb.com

Technical documentation

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

en.gstore.cn/#/enDocs

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

docs.voltdb.com

Developer

CCRi and others

Apache Software Foundation

Transaction Software GmbH

VoltDB Inc.

Initial release

2014

2016

2014

1987

2010

Current release

5.0.0, May 2024

1.2, November 2023

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD

Open Source

Apache 2.0

commercial

free development license

Open Source

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

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C++

Scala

C and C++

Java, C++

Server operating systems

Linux

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X

for development

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

only a subset of SQL 99

APIs and other access methods

HTTP API
SPARQL 1.1

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

yes, utilizing Spark Core

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Source-replica replication

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

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

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

Users, roles and permissions, Role-Based Access Control (RBAC) supported

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Performance Insights from Sigma Rule Detections in Spark Streaming
1 June 2024, Towards Data Science

Run Apache Hive workloads using Spark SQL with Amazon EMR on EKS | Amazon Web Services
18 October 2023, AWS Blog

What is Apache Spark? The big data platform that crushed Hadoop
3 April 2024, InfoWorld

Cracking the Apache Spark Interview: 80+ Top Questions and Answers for 2024
1 April 2024, Simplilearn

Use Amazon Athena with Spark SQL for your open-source transactional table formats | Amazon Web Services
24 January 2024, AWS Blog

provided by Google News

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

VoltDB Aims for Fast Big Data Development -- ADTmag
29 January 2015, ADT Magazine

Stonebraker Seeks to Invert the Computing Paradigm with DBOS
12 March 2024, Datanami

provided by Google News

Share this page