DBMS > Netezza vs. RDF4J vs. Snowflake vs. VelocityDB vs. VoltDB

System Properties Comparison Netezza vs. RDF4J vs. Snowflake vs. VelocityDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Data warehouse and analytics appliance part of IBM PureSystems

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

RDF store

Relational DBMS

Graph DBMS
Object oriented DBMS

Relational DBMS

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

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.ibm.com/products/netezza

Technical documentation

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

velocitydb.com/UserGuide

docs.voltdb.com

Developer

IBM

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

VelocityDB Inc

VoltDB Inc.

Initial release

2000

2004

2014

2011

2010

Current release

7.x

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux

included in appliance

Linux
OS X
Unix
Windows

hosted

Any that supports .NET

Linux
OS X

for development

Data scheme

yes

RDF Schemas

yes

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

yes

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

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC
OLE DB

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

.Net

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Fortran
Java
Lua
Perl
Python
R

Java
PHP
Python

JavaScript (Node.js)
Python

.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

Java

Triggers

yes

similar concept for controling cloud resources

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Isolation support depends on the API used

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Users with fine-grained authorization concept

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

Based on Windows Authentication

Users and roles with access to stored procedures

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.