DBMS > AnzoGraph DB vs. jBASE vs. Netezza vs. Prometheus vs. Snowflake

System Properties Comparison AnzoGraph DB vs. jBASE vs. Netezza vs. Prometheus 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

A robust multi-value DBMS comprising development tools and middleware

Data warehouse and analytics appliance part of IBM PureSystems

Open-source Time Series DBMS and monitoring system

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	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

cambridgesemantics.com/anzograph

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.ibm.com/products/netezza

prometheus.io

www.snowflake.com

Technical documentation

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

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

prometheus.io/docs

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

Rocket Software (formerly Zumasys)

IBM

Snowflake Computing Inc.

Initial release

2018

1991

2000

2015

2014

Current release

2.3, January 2021

5.7

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

Apache 2.0

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

Server operating systems

Linux

AIX
Linux
Windows

Linux

included in appliance

Linux
Windows

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

schema-free

yes

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

Typing

predefined data types such as float or date

optional

yes

Numeric data only

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

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

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

Embedded SQL for jBASE in BASIC

yes

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

JDBC
ODBC
OLE DB

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Python

.Net
Basic
Jabbascript
Java

C
C++
Fortran
Java
Lua
Perl
Python
R

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

yes

Source-replica replication

yes

by Federation

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

none

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

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 can be defined down to the item level

Users with fine-grained authorization concept

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.