DBMS > AnzoGraph DB vs. GeoSpock vs. GridDB vs. MaxDB vs. Snowflake

System Properties Comparison AnzoGraph DB vs. GeoSpock vs. GridDB vs. MaxDB vs. Snowflake

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

Scalable in-memory time series database optimized for IoT and Big Data

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

Secondary database models

Time Series DBMS

Key-value store
Relational DBMS

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	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cambridgesemantics.com/anzograph

geospock.com

griddb.net

maxdb.sap.com

www.snowflake.com

Technical documentation

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

docs.griddb.net

maxdb.sap.com/documentation

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

GeoSpock

Toshiba Corporation

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

Snowflake Computing Inc.

Initial release

2018

2013

1984

2014

Current release

2.3, January 2021

2.0, September 2019

5.1, August 2022

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

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, Javascript

C++

Server operating systems

Linux

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

yes

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

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

temporal, categorical

yes

SQL

Support of SQL

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

ANSI SQL for query only (using Presto)

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

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

JDBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
WebDAV

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Python

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
C#
Java
Perl
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

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

ACID at container level

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 for users can be defined per table

Access rights for users can be defined per database

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

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.