DBMS > GeoSpock vs. GridGain vs. Percona Server for MongoDB vs. Snowflake

System Properties Comparison GeoSpock vs. GridGain vs. Percona Server for MongoDB vs. Snowflake

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.

Description

Spatial and temporal data processing engine for extreme data scale

GridGain is an in-memory computing platform, built on Apache Ignite

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

Primary database model

Relational DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Document store

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.50
Rank	#250	Overall
	#39	Document stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

geospock.com

www.gridgain.com

www.percona.com/mongodb/software/percona-server-for-mongodb

www.snowflake.com

Technical documentation

www.gridgain.com/docs/index.html

docs.percona.com/percona-distribution-for-mongodb

docs.snowflake.net/manuals/index.html

Developer

GeoSpock

GridGain Systems, Inc.

Percona

Snowflake Computing Inc.

Initial release

2007

2015

2014

Current release

2.0, September 2019

GridGain 8.5.1

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

commercial, open source

Open Source

GPL Version 2

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, C++, .Net, Python, REST, SQL

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows
z/OS

Linux

hosted

Data scheme

yes

schema-free

yes

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

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)

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

JDBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

proprietary protocol using JSON

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

JavaScript

user defined functions

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

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

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

via In-Memory Engine

User concepts

Access control

Access rights for users can be defined per table

Role-based access control
Security Hooks for custom implementations

Access rights for users and roles

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.