DBMS > Amazon DynamoDB vs. Graph Engine vs. jBASE vs. RRDtool

System Properties Comparison Amazon DynamoDB vs. Graph Engine vs. jBASE vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A robust multi-value DBMS comprising development tools and middleware

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

Document store
Key-value store

Graph DBMS
Key-value store

Multivalue DBMS

Time Series DBMS

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.43
Rank	#160	Overall
	#3	Multivalue DBMS

Score	2.14
Rank	#124	Overall
	#10	Time Series DBMS

Website

aws.amazon.com/dynamodb

www.graphengine.io

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

oss.oetiker.ch/rrdtool

Technical documentation

docs.aws.amazon.com/dynamodb

www.graphengine.io/docs/manual

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

oss.oetiker.ch/rrdtool/doc

Developer

Amazon

Microsoft

Rocket Software (formerly Zumasys)

Tobias Oetiker

Initial release

2012

2010

1991

1999

Current release

5.7

1.8.0, 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

MIT License

commercial

Open Source

GPL V2 and FLOSS

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

.NET and C

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

Server operating systems

hosted

.NET

AIX
Linux
Windows

HP-UX
Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

optional

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

Embedded SQL for jBASE in BASIC

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

in-process shared library
Pipes

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
C++
F#
Visual Basic

.Net
Basic
Jabbascript
Java

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

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

none

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent 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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Access rights can be defined down to the item level

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.