DBMS > Hive vs. IRONdb vs. RDF4J vs. Redis vs. YugabyteDB

System Properties Comparison Hive vs. IRONdb vs. RDF4J vs. Redis vs. YugabyteDB

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

data warehouse software for querying and managing large distributed datasets, built on Hadoop

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Relational DBMS

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Document store
Wide column store

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

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Score	2.91
Rank	#102	Overall
	#51	Relational DBMS

Website

hive.apache.org

www.circonus.com/solutions/time-series-database/

rdf4j.org

redis.com
redis.io

www.yugabyte.com

Technical documentation

cwiki.apache.org/confluence/display/Hive/Home

docs.circonus.com/irondb/category/getting-started

rdf4j.org/documentation

docs.redis.com/latest/index.html
redis.io/docs

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

Apache Software Foundation

initially developed by Facebook

Circonus LLC.

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Yugabyte Inc.

Initial release

2012

2017

2004

2009

2017

Current release

3.1.3, April 2022

V0.10.20, January 2018

7.2.4, January 2024

2.19, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

Open Source

Apache 2.0

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 Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

YugabyteDB Managed is the fully managed database-as-a-service offering of YugabyteDB. Get started quickly, and effortlessly ensure continuous availability and limitless scale of your cloud native applications.

Implementation language

Java

C and C++

Java

C and C++

Server operating systems

All OS with a Java VM

Linux

Linux
OS X
Unix
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X

Data scheme

yes

schema-free

yes

RDF Schemas

schema-free

depending on used data model

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

Secondary indexes

yes

with RediSearch module

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language (Circonus Analytics Query Language: CAQL)

with RediSQL module

yes, PostgreSQL compatible

APIs and other access methods

JDBC
ODBC
Thrift

HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

C++
Java
PHP
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Java
PHP
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes, in Lua

yes

Lua; Redis Functions coming in Redis 7 (slides and Github)

yes

sql, plpgsql, C

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

none

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

configurable replication factor, datacenter aware

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Strong consistency on writes and tunable consistency on reads

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

Atomic execution of command blocks and scripts and optimistic locking

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

based on RocksDB

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, groups and roles

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

yes

More information provided by the system vendor

Specific characteristics

YugabyteDB is an open source distributed SQL database for cloud native transactional...
» more

Competitive advantages

PostgreSQL compatible: Get instantly productive with a PostgreSQL compatible RDBMS....
» more

Typical application scenarios

Systems of record and engagement for cloud native applications that require resilience,...
» more

Market metrics

2 Million+ lifetime clusters deployed, 6.5K+ GitHub stars, 7K YugabyteDB Community...
» more

Licensing and pricing models

Apache 2.0 license for the database
» more

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.