DBMS > Couchbase vs. GraphDB vs. IBM Db2 vs. Ignite vs. Redis

System Properties Comparison Couchbase vs. GraphDB vs. IBM Db2 vs. Ignite vs. Redis

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

Common in IBM host environments, 2 different versions for host and Windows/Linux

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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.

Primary database model

Document store

Graph DBMS
RDF store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store
Relational DBMS

Key-value store

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

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	3.25
Rank	#91	Overall
	#7	Graph DBMS
	#4	RDF stores

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Website

www.couchbase.com

www.ontotext.com

www.ibm.com/products/db2

ignite.apache.org

redis.com
redis.io

Technical documentation

docs.couchbase.com

graphdb.ontotext.com/documentation

www.ibm.com/docs/en/db2

apacheignite.readme.io/docs

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

Social network pages

Developer

Couchbase, Inc.

Ontotext

IBM

Apache Software Foundation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2011

2000

1983

host version

2015

2009

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

10.4, October 2023

12.1, October 2016

Apache Ignite 2.6

7.2.5, May 2024

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

Some plugins of GraphDB Workbench are open sourced

commercial

free version is available

Open Source

Apache 2.0

Open Source

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

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.

Implementation language

C, C++, Go and Erlang

Java

C and C++

C++, Java, .Net

Server operating systems

Linux
OS X
Windows

All OS with a Java VM
Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

schema-free and OWL/RDFS-schema support; RDF shapes

yes

schema-free

Typing

predefined data types such as float or date

yes

partial

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

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

Secondary indexes

yes

yes, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

with RediSearch module

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

yes

ANSI-99 for query and DML statements, subset of DDL

with RediSQL module

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
C#
Clojure
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C#
C++
Java
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

well-defined plugin interfaces; JavaScript server-side extensibility

yes

yes (compute grid and cache interceptors can be used instead)

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

Triggers

yes

via the TAP protocol

yes

yes (cache interceptors and events)

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

Sharding

only with Windows/Unix/Linux Version

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication

yes

with separate tools (MQ, InfoSphere)

yes (replicated cache)

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Immediate Consistency

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

Foreign keys

Referential integrity

yes

Constraint checking

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

In-memory capabilities

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

yes

Ephemeral buckets

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

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

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

News

Matching Skills and Candidates with Graph RAG
31 May 2024

A Triple Store RAG Retriever
29 May 2024

Integrating GraphDB with Relational Database Systems
23 May 2024

Understanding the Graph Center of Excellence
17 May 2024

Migrating From LPG to RDF Graph Model
8 May 2024

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.