DBMS > Geode vs. Sadas Engine vs. Snowflake vs. Titan

System Properties Comparison Geode vs. Sadas Engine vs. Snowflake vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Key-value store

Relational DBMS

Graph DBMS

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

geode.apache.org

www.sadasengine.com

www.snowflake.com

github.com/thinkaurelius/titan

Technical documentation

geode.apache.org/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

docs.snowflake.net/manuals/index.html

github.com/thinkaurelius/titan/wiki

Developer

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

SADAS s.r.l.

Snowflake Computing Inc.

Aurelius, owned by DataStax

Initial release

2002

2006

2014

2012

Current release

1.1, February 2017

8.0

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free trial version available

commercial

Open Source

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

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
Linux
Windows

hosted

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

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

yes

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

SQL

Support of SQL

SQL-like query language (OQL)

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Proprietary protocol

CLI Client
JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

JavaScript (Node.js)
Python

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

managed by 'Learn by Usage'

User concepts

Access control

Access rights per client and object definable

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

User authentification and security via Rexster Graph Server

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.