DBMS > Graphite vs. PostgreSQL vs. Riak TS

System Properties Comparison Graphite vs. PostgreSQL vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Time Series DBMS

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

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

Score	4.55
Rank	#63	Overall
	#4	Time Series DBMS

Score	663.41
Rank	#4	Overall
	#4	Relational DBMS

Score	0.16
Rank	#320	Overall
	#27	Time Series DBMS

Website

github.com/graphite-project/graphite-web

www.postgresql.org

Technical documentation

graphite.readthedocs.io

www.postgresql.org/docs

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

Developer

Chris Davis

PostgreSQL Global Development Group

www.postgresql.org/developer

Open Source, formerly Basho Technologies

Initial release

2006

1989

1989: Postgres, 1996: PostgreSQL

2015

Current release

16.4, August 2024

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD

Open Source

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

Python

Erlang

Server operating systems

Linux
Unix

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

Linux
OS X

Data scheme

yes

schema-free

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.

yes

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

standard with numerous extensions

yes, limited

APIs and other access methods

HTTP API
Sockets

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API
Native Erlang Interface

Supported programming languages

JavaScript (Node.js)
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

partitioning by range, list and (since PostgreSQL 11) by hash

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

other methods possible by using 3rd party extensions

selectable replication factor

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

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

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.

User concepts

Access control

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.