DBMS > CockroachDB vs. RDF4J vs. Riak KV

System Properties Comparison CockroachDB vs. RDF4J vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

RDF store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

www.cockroachlabs.com

rdf4j.org

Technical documentation

www.cockroachlabs.com/docs

rdf4j.org/documentation

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

Developer

Cockroach Labs

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

OpenSource, formerly Basho Technologies

Initial release

2015

2004

2009

Current release

23.1.1, May 2023

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Apache version 2, commercial enterprise edition

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.

Implementation language

Java

Erlang

Server operating systems

Linux
macOS
Windows

Linux
OS X
Unix
Windows

Linux
OS X

Data scheme

dynamic schema

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

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

restricted

SQL

Support of SQL

yes, wire compatible with PostgreSQL

APIs and other access methods

JDBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP API
Native Erlang Interface

Supported programming languages

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

Java
PHP
Python

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

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

none

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Role-based access control

yes, using Riak Security

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

CockroachDB 23.2 Enhances Enterprise Architectures with Improved Postgres Compatibility and Built-in Resilience
18 January 2024, PR Newswire

CockroachDB tempts legacy databases to crawl into the cloud age
29 January 2024, The Register

How to Unlock Real-Time Data Streams with CockroachDB and Amazon MSK | Amazon Web Services
6 November 2023, AWS Blog

How DoorDash Migrated from Aurora Postgres to CockroachDB
5 December 2023, The New Stack

CockroachDB's Latest Enhancements Focus on Resilience
18 January 2024, Database Trends and Applications

provided by Google News

GraphDB Goes Open Source
27 January 2020, iProgrammer

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page