DBMS > AnzoGraph DB vs. Netezza vs. Snowflake vs. Warp 10 vs. XTDB

System Properties Comparison AnzoGraph DB vs. Netezza vs. Snowflake vs. Warp 10 vs. XTDB

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

Data warehouse and analytics appliance part of IBM PureSystems

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

A general purpose database with bitemporal SQL and Datalog and graph queries

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	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

cambridgesemantics.com/anzograph

www.ibm.com/products/netezza

www.snowflake.com

www.warp10.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

docs.snowflake.net/manuals/index.html

www.warp10.io/content/02_Getting_started

www.xtdb.com/docs

Developer

Cambridge Semantics

IBM

Snowflake Computing Inc.

SenX

Juxt Ltd.

Initial release

2018

2000

2014

2015

2019

Current release

2.3, January 2021

1.19, September 2021

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

Apache License 2.0

Open Source

MIT License

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

Clojure

Server operating systems

Linux

included in appliance

hosted

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

Schema-free and OWL/RDFS-schema support

yes

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

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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.

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

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

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

HTTP API
Jupyter
WebSocket

HTTP REST
JDBC

Supported programming languages

C++
Java
Python

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

user defined functions

yes

WarpScript

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

yes

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

Source-replica replication

yes

selectable replication factor

based on HBase

yes, each node contains all data

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

Immediate Consistency

based on HBase

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Users with fine-grained authorization concept

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.