DBMS > CouchDB vs. Heroic vs. RDF4J vs. Sequoiadb

System Properties Comparison CouchDB vs. Heroic vs. RDF4J vs. Sequoiadb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

NewSQL database with distributed OLTP and SQL

Primary database model

Document store

Time Series DBMS

RDF store

Document store
Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Score	0.48
Rank	#260	Overall
	#41	Document stores
	#121	Relational DBMS

Website

couchdb.apache.org

github.com/spotify/heroic

rdf4j.org

www.sequoiadb.com

Technical documentation

docs.couchdb.org/en/stable

spotify.github.io/heroic

rdf4j.org/documentation

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Spotify

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

Sequoiadb Ltd.

Initial release

2005

2014

2004

2013

Current release

3.3.3, December 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Server: AGPL; Client: Apache V2

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

Erlang

Java

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Linux

Data scheme

schema-free

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

via views

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

proprietary protocol using JSON

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Java
PHP
Python

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

View functions in JavaScript

yes

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

ACID

Isolation support depends on the API used

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

simple password-based access control

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

DB-Engines blog posts

Couchbase climbs up the DB-Engines Ranking, increasing its popularity by 10% every month
2 June 2014, Matthias Gelbmann

show all

Recent citations in the news

How to install the CouchDB NoSQL database on Debian Server 11
16 June 2022, TechRepublic

IBM Cloudant pulls plan to fund new foundational layer for CouchDB
15 March 2022, The Register

CouchDB 3.0 ends admin party era • DEVCLASS
27 February 2020, DevClass

CouchDB 3.0 puts safety first
27 February 2020, InfoWorld

How to Connect Your Flask App With CouchDB: A NoSQL Database - MUO
14 August 2021, MakeUseOf

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Share this page