DBMS > Netezza vs. Riak KV vs. Snowflake vs. XTDB

System Properties Comparison Netezza vs. Riak KV vs. Snowflake vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Data warehouse and analytics appliance part of IBM PureSystems

Distributed, fault tolerant key-value store

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

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

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Document store

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

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.ibm.com/products/netezza

www.snowflake.com

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

Technical documentation

www.tiot.jp/riak-docs/riak/kv/latest

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

IBM

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Juxt Ltd.

Initial release

2000

2009

2014

2019

Current release

3.2.0, December 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

commercial

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

Erlang

Clojure

Server operating systems

Linux

included in appliance

Linux
OS X

hosted

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

Data scheme

yes

schema-free

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

restricted

yes

SQL

Support of SQL

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC
OLE DB

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

C
C++
Fortran
Java
Lua
Perl
Python
R

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

Erlang

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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.

User concepts

Access control

Users with fine-grained authorization concept

yes, using Riak Security

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.