DBMS > DataFS vs. Geode vs. IBM Db2 warehouse vs. Snowflake

System Properties Comparison DataFS vs. Geode vs. IBM Db2 warehouse vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Cloud-based data warehousing service

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

Primary database model

Object oriented DBMS

Key-value store

Relational DBMS

Secondary database models

Graph DBMS

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

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

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

newdatabase.com

geode.apache.org

www.ibm.com/products/db2/warehouse

www.snowflake.com

Technical documentation

dev.mobiland.com/Overview.xsp

geode.apache.org/docs

docs.snowflake.net/manuals/index.html

Developer

Mobiland AG

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

IBM

Snowflake Computing Inc.

Initial release

2018

2002

2014

Current release

1.1.263, October 2022

1.1, February 2017

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

Server operating systems

Windows

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

Java Client API
Memcached protocol
RESTful HTTP API

.NET Client API
JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
VB.Net

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

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

PL/SQL, SQL PL

user defined functions

Triggers

no, except callback-events from server when changes happened

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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

Windows-Profile

Access rights per client and object definable

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.