DBMS > Amazon CloudSearch vs. Geode vs. GridGain vs. SAP IQ vs. Snowflake

System Properties Comparison Amazon CloudSearch vs. Geode vs. GridGain vs. SAP IQ vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Columnar RDBMS optimized for Big Data analytics

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

Primary database model

Search engine

Key-value store

Key-value store
Relational DBMS

Relational DBMS

column-oriented

Relational DBMS

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

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	2.75
Rank	#104	Overall
	#53	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/cloudsearch

geode.apache.org

www.gridgain.com

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.snowflake.com

Technical documentation

docs.aws.amazon.com/cloudsearch

geode.apache.org/docs

www.gridgain.com/docs/index.html

help.sap.com/docs/SAP_IQ

docs.snowflake.net/manuals/index.html

Developer

Amazon

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

GridGain Systems, Inc.

SAP, formerly Sybase

Snowflake Computing Inc.

Initial release

2012

2002

2007

1994

2014

Current release

1.1, February 2017

GridGain 8.5.1

16.1 SPS04, April 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java, C++, .Net

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

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

yes

all search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (OQL)

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

yes

APIs and other access methods

HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

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

ADO.NET
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Java
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

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

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Sharding

shared disk or shared nothing architectures with SAP IQ Multiplexer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication

yes (replicated cache)

SAP/Sybase Replication Server

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

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

User concepts

Access control

authentication via encrypted signatures

Access rights per client and object definable

Security Hooks for custom implementations

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.