DBMS > Google Cloud Datastore vs. GridGain vs. STSdb vs. WakandaDB

System Properties Comparison Google Cloud Datastore vs. GridGain vs. STSdb vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store

Key-value store
Relational DBMS

Key-value store

Object oriented DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

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

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

cloud.google.com/datastore

www.gridgain.com

github.com/STSSoft/STSdb4

wakanda.github.io

Technical documentation

cloud.google.com/datastore/docs

www.gridgain.com/docs/index.html

wakanda.github.io/doc

Developer

Google

GridGain Systems, Inc.

STS Soft SC

Wakanda SAS

Initial release

2008

2007

2011

2012

Current release

GridGain 8.5.1

4.0.8, September 2015

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

GPLv2, commercial license available

Open Source

AGPLv3, extended commercial license available

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

C++, JavaScript

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes, details here

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

SQL-like query language (GQL)

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

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

.NET Client API

RESTful HTTP API

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java

JavaScript

Server-side scripts

Stored procedures

using Google App Engine

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

yes

Triggers

Callbacks using the Google Apps Engine

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Security Hooks for custom implementations

yes

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
29 April 2024, TechRadar

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks & Files

GridGain to Sponsor and Speak at Three Key Industry Events in May 2024
6 May 2024, Martechcube

GridGain's 2023 Growth Positions Company for Strong 2024
25 January 2024, Datanami

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Named in the 2023 Gartner® Market Guide for Event Stream Processing
22 August 2023, GlobeNewswire

provided by Google News

Share this page