DBMS > Geode vs. Google Cloud Datastore vs. STSdb vs. Trafodion

System Properties Comparison Geode vs. Google Cloud Datastore vs. STSdb vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Transactional SQL-on-Hadoop DBMS

Primary database model

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

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

geode.apache.org

cloud.google.com/datastore

github.com/STSSoft/STSdb4

trafodion.apache.org

Technical documentation

geode.apache.org/docs

cloud.google.com/datastore/docs

trafodion.apache.org/documentation.html

Developer

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

Google

STS Soft SC

Apache Software Foundation, originally developed by HP

Initial release

2002

2008

2011

2014

Current release

1.1, February 2017

4.0.8, September 2015

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPLv2, commercial license available

Open Source

Apache 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++, Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language (GQL)

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

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

.NET Client API

ADO.NET
JDBC
ODBC

Supported programming languages

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

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

C#
Java

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

Java Stored Procedures

Triggers

yes

Cache Event Listeners

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using Paxos

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

yes

Transaction concepts

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

yes, on a single node

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 per client and object definable

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

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.

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

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns ‘All Sorts of In-Memory Things’
4 January 2017, The New Stack

Chapter 1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode
15 November 2018, O'Reilly Media

RDBMS and Apache Geode Data Movement: Low Latency ETL Pipeline by Using Cloud-Native Event Driven Microservices
30 June 2018, InfoQ.com

HPE buys query acceleration platform Ampool to boost Ezmeral hybrid cloud analytics
7 July 2021, SiliconANGLE News

provided by Google News

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Best cloud storage of 2024
13 September 2024, TechRadar

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Google App Engine
26 April 2024, TechTarget

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

Share this page