DBMS > GridGain vs. Memcached vs. Snowflake vs. SQream DB vs. Tkrzw

System Properties Comparison GridGain vs. Memcached vs. Snowflake vs. SQream DB vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

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

In-memory key-value store, originally intended for caching

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

a GPU-based, columnar RDBMS for big data analytics workloads

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

Relational DBMS

Key-value store

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	16.84
Rank	#32	Overall
	#4	Key-value stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.62
Rank	#234	Overall
	#109	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

Technical documentation

www.gridgain.com/docs/index.html

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

docs.sqream.com

Developer

GridGain Systems, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

SQream Technologies

Mikio Hirabayashi

Initial release

2007

2003

2014

2017

2020

Current release

GridGain 8.5.1

1.6.29, June 2024

2022.1.6, December 2022

0.9.3, August 2020

License

Commercial or Open Source

commercial, open source

Open Source

BSD license

commercial

Open Source

Apache Version 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

Java, C++, .Net, Python, REST, SQL

C++, CUDA, Haskell, Java, Scala

C++

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Unix
Windows

hosted

Linux

Linux
macOS

Data scheme

yes

schema-free

yes

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

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

SQL

Support of SQL

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

yes

APIs and other access methods

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

Proprietary protocol

CLI Client
JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

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

user defined functions

user defined functions in Python

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

horizontal and vertical partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

Repcached, a Memcached patch, provides this functionallity

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

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

using specific database classes

User concepts

Access control

Role-based access control
Security Hooks for custom implementations

yes

using SASL (Simple Authentication and Security Layer) protocol

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.