DBMS > IBM Db2 Event Store vs. Netezza vs. RRDtool vs. Snowflake

System Properties Comparison IBM Db2 Event Store vs. Netezza vs. RRDtool vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Event Store optimized for Internet of Things use cases

Data warehouse and analytics appliance part of IBM PureSystems

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

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

Primary database model

Event Store
Time Series DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.ibm.com/products/db2-event-store

www.ibm.com/products/netezza

oss.oetiker.ch/rrdtool

www.snowflake.com

Technical documentation

www.ibm.com/docs/en/db2-event-store

oss.oetiker.ch/rrdtool/doc

docs.snowflake.net/manuals/index.html

Developer

IBM

Tobias Oetiker

Snowflake Computing Inc.

Initial release

2017

2000

1999

2014

Current release

2.0

1.8.0, 2022

License

Commercial or Open Source

commercial

free developer edition available

commercial

Open Source

GPL V2 and FLOSS

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

C and C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

Linux

included in appliance

HP-UX
Linux

hosted

Data scheme

yes

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

Typing

predefined data types such as float or date

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.

Exporting into and restoring from XML files possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

APIs and other access methods

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
OLE DB

in-process shared library
Pipes

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

C
C++
Fortran
Java
Lua
Perl
Python
R

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Active-active shard replication

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

No - written data is immutable

yes

by using the rrdcached daemon

yes

Durability

Support for making data persistent

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

fine grained access rights according to SQL-standard

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.