DBMS > RRDtool vs. Snowflake vs. Splunk vs. Teradata

System Properties Comparison RRDtool vs. Snowflake vs. Splunk vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Analytics Platform for Big Data

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

oss.oetiker.ch/rrdtool

www.snowflake.com

www.splunk.com

www.teradata.com

Technical documentation

oss.oetiker.ch/rrdtool/doc

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

docs.teradata.com

Developer

Tobias Oetiker

Snowflake Computing Inc.

Splunk Inc.

Teradata

Initial release

1999

2014

2003

1984

Current release

1.8.0, 2022

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

GPL V2 and FLOSS

commercial

Limited free edition and free developer edition available

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

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

Server operating systems

HP-UX
Linux

hosted

Linux
OS X
Solaris
Windows

hosted
Linux

Data scheme

yes

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

yes

Typing

predefined data types such as float or date

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

yes

SQL 2016 + extensions

APIs and other access methods

in-process shared library
Pipes

CLI Client
JDBC
ODBC

HTTP REST

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

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

C#
Java
JavaScript
PHP
Python
Ruby

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication

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

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

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

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

Access rights for users and roles

fine grained access rights according to SQL-standard

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.