DBMS > AnzoGraph DB vs. Blueflood vs. Geode vs. MaxDB vs. Snowflake

System Properties Comparison AnzoGraph DB vs. Blueflood vs. Geode vs. MaxDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

Scalable TimeSeries DBMS based on Cassandra

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

A robust and reliable RDBMS optimized to run all major SAP solutions

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

Primary database model

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

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

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

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cambridgesemantics.com/anzograph

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

github.com/rax-maas/blueflood/wiki

geode.apache.org/docs

maxdb.sap.com/documentation

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

Rackspace

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

SAP, acquired from Software AG (Adabas-D) in 1997

Snowflake Computing Inc.

Initial release

2018

2013

2002

1984

2014

Current release

2.3, January 2021

1.1, February 2017

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

free trial version available

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Limited community edition free

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

C++

Server operating systems

Linux

Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

predefined scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SPARQL and SPARQL* as primary query language. Cypher preview.

SQL-like query language (OQL)

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

HTTP REST

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
WebDAV

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Python

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

.Net
C#
Java
Perl
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

yes

user defined functions

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

based on Cassandra

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

selectable replication factor

based on Cassandra

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

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

Access rights for users and roles

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.