DBMS > GeoSpock vs. OpenQM vs. Snowflake vs. Splice Machine vs. Valentina Server

System Properties Comparison GeoSpock vs. OpenQM vs. Snowflake vs. Splice Machine vs. Valentina Server

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

Cloud-based data warehousing service for structured and semi-structured data

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Object-relational database and reports server

Primary database model

Relational DBMS

Multivalue DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

geospock.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.snowflake.com

splicemachine.com

www.valentina-db.net

Technical documentation

docs.snowflake.net/manuals/index.html

splicemachine.com/how-it-works

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

GeoSpock

Rocket Software, originally Martin Phillips

Snowflake Computing Inc.

Splice Machine

Paradigma Software

Initial release

1993

2014

1999

Current release

2.0, September 2019

3.4-12

3.1, March 2021

5.7.5

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

commercial

Open Source

AGPL 3.0, commercial license available

commercial

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

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

hosted

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

with some exceptions

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC

CLI Client
JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

ODBC

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript (Node.js)
Python

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

user defined functions

yes

Java

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

yes

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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 rights can be defined down to the item level

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users, groups and roles according to SQL-standard

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.