DBMS > GeoSpock vs. GridGain vs. PouchDB vs. Snowflake vs. Yaacomo

System Properties Comparison GeoSpock vs. GridGain vs. PouchDB vs. Snowflake vs. Yaacomo

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Yaacomo seems to be discontinued and is removed 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

JavaScript DBMS with an API inspired by CouchDB

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Key-value store
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.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

geospock.com

www.gridgain.com

pouchdb.com

www.snowflake.com

yaacomo.com

Technical documentation

www.gridgain.com/docs/index.html

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

Developer

GeoSpock

GridGain Systems, Inc.

Apache Software Foundation

Snowflake Computing Inc.

Q2WEB GmbH

Initial release

2007

2012

2014

2009

Current release

2.0, September 2019

GridGain 8.5.1

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

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

JavaScript

Server operating systems

hosted

Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Android
Linux
Windows

Data scheme

yes

schema-free

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

via views

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

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

View functions in JavaScript

user defined functions

Triggers

yes (cache interceptors and events)

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

with a proxy-based framework, named couchdb-lounge

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

Source-replica replication

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

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

by using IndexedDB, WebSQL or LevelDB as backend

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

Security Hooks for custom implementations

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

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.