DBMS > GeoMesa vs. Greenplum vs. InfinityDB vs. Snowflake vs. Spark SQL

System Properties Comparison GeoMesa vs. Greenplum vs. InfinityDB vs. Snowflake vs. Spark SQL

Editorial information provided by DB-Engines

Name

Description

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

A Java embedded Key-Value Store which extends the Java Map interface

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

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

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

Technical documentation

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

docs.greenplum.org

boilerbay.com/infinitydb/manual

docs.snowflake.net/manuals/index.html

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

Developer

CCRi and others

Pivotal Software Inc.

Boiler Bay Inc.

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2014

2005

2002

2014

Current release

5.0.0, May 2024

7.0.0, September 2023

4.0

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

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

Scala

Java

Scala

Server operating systems

Linux

All OS with a Java VM

hosted

Linux
OS X
Windows

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

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

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

since Version 4.2

yes

Secondary indexes

yes

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C
Java
Perl
Python
R

Java

JavaScript (Node.js)
Python

Java
Python
R
Scala

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

none

yes

none

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

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

yes

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

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.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

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

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.