DBMS > AgensGraph vs. JaguarDB vs. MySQL vs. RRDtool

System Properties Comparison AgensGraph vs. JaguarDB vs. MySQL vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Performant, highly scalable DBMS for AI and IoT applications

Widely used open source RDBMS

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.

Primary database model

Graph DBMS
Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Website

bitnine.net/agensgraph

www.jaguardb.com

www.mysql.com

oss.oetiker.ch/rrdtool

Technical documentation

bitnine.net/documentation

www.jaguardb.com/support.html

dev.mysql.com/doc

oss.oetiker.ch/rrdtool/doc

Developer

Bitnine Global Inc.

DataJaguar, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Tobias Oetiker

Initial release

2016

2015

1995

1999

Current release

2.1, December 2018

3.3 July 2023

8.4.0, April 2024

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL V3.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V2 and FLOSS

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

the server part. Clients available in other languages

C and C++

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

Server operating systems

Linux
OS X
Windows

Linux

FreeBSD
Linux
OS X
Solaris
Windows

HP-UX
Linux

Data scheme

depending on used data model

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

in-process shared library
Pipes

Supported programming languages

C
Java
JavaScript
Python

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

by using the rrdcached daemon

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

fine grained access rights according to SQL-standard

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

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.