Resilience Patterns with Resilience4j

Latest stable Based on Bluetape4k release 1.11.0

Problem

Resilience4j is a lightweight, fault-tolerance library for isolation and recovery. This manual connects that purpose to the current build, source entry points, tests, configuration resources, and lifecycle evidence instead of duplicating the README feature list.

When to use

Use bluetape4k-resilience4j when the application needs client lifecycle, reconnect policy, backpressure, retries, and observability. Start with the source entry points below and confirm that their ownership and failure contracts match the calling component. Prefer a smaller standard-library or already-adopted module when it satisfies the same contract without another runtime boundary.

Coordinates

dependencies {
    implementation(platform("io.github.bluetape4k:bluetape4k-dependencies:<version>"))
    implementation("io.github.bluetape4k:bluetape4k-resilience4j")
}

Gradle project path: :bluetape4k-resilience4j. Source directory: infra/resilience4j.

Concepts

The first source-level concepts to inspect are RetryAsyncContextBridge, CallableSupport, CancellationSupport, CompletionStageSupport, DecoratorsSupport, SupplierSupport, SuspendDecorators, and SuspendSupplierExtensions. File names are navigation anchors; read each declaration and its tests before treating it as a public contract.

Quick start

Add the coordinate above, refresh Gradle, and start from the smallest entry point that owns the required task. Open RetryAsyncContextBridge first; it is a concrete source entry point for the module.

API by task

Entry point	What to verify
`RetryAsyncContextBridge`	Inspect this declaration’s constructors, functions, and ownership contract.
`CallableSupport`	Inspect this declaration’s constructors, functions, and ownership contract.
`CancellationSupport`	Inspect this declaration’s constructors, functions, and ownership contract.
`CompletionStageSupport`	Inspect this declaration’s constructors, functions, and ownership contract.
`DecoratorsSupport`	Inspect this declaration’s constructors, functions, and ownership contract.
`SupplierSupport`	Inspect this declaration’s constructors, functions, and ownership contract.
`SuspendDecorators`	Inspect this declaration’s constructors, functions, and ownership contract.
`SuspendSupplierExtensions`	Inspect this declaration’s constructors, functions, and ownership contract.
`BulkheadCoroutines`	Inspect this declaration’s constructors, functions, and ownership contract.
`BulkheadExtensions`	Inspect this declaration’s constructors, functions, and ownership contract.

Patterns

The README evidence is organized around Class Structure, Resilience4j Coroutine Class Structure, Architecture, CircuitBreaker + Retry Combination Sequence Diagram, SuspendCache Operation Sequence Diagram, Features, Module Boundary, Coroutine Contract, Dependency, and Key Features. Use those topics as a navigation map, then confirm behavior in source and tests. Keep adoption narrow and connect owned resources to the caller lifecycle.

Integrations

The current build declares these integration edges:

api(project(":bluetape4k-core"))
compileOnly(project(":bluetape4k-coroutines"))
compileOnly(project(":bluetape4k-cache-redisson"))
api(libs.resilience4j.all)
api(libs.resilience4j.cache)
api(libs.resilience4j.kotlin)
compileOnly(libs.resilience4j.reactor)
compileOnly(libs.resilience4j.micrometer)
compileOnly(libs.kotlinx.coroutines.core)
compileOnly(libs.kotlinx.coroutines.reactor)

Treat compileOnly edges as caller-provided capabilities and verify runtime availability before using their APIs.

Configuration

No module-level configuration resource was found under src/main/resources. Configuration is supplied through constructors, builders, function arguments, or the integrating framework; confirm defaults in source.

Failures

Failure semantics are defined by the linked entry points and tests, not inferred from the artifact name. Keep cancellation and timeout signals intact, close owned resources, and translate backend exceptions only at a boundary that can add a stable domain contract. Use the test anchors below to verify the exact behavior before adding retries or fallbacks.

Operations

Track connection state, queue depth, retries, timeouts, remote errors, and graceful shutdown. Keep capacity, timeout, retry, and shutdown settings next to the component that owns the resource; avoid process-wide defaults that hide which caller accepted the trade-off.

Testing

Run the module test task:

./gradlew :bluetape4k-resilience4j:test --no-configuration-cache

Representative test anchors:

Workshops

No dedicated workshop path is registered in the manual manifest. Use the module README and the representative tests above as runnable evidence.

Limitations

This page documents the repository state represented by the linked source and tests. It does not turn optional backends into application defaults or claim performance without a benchmark artifact. Re-check compatibility and lifecycle notes when the module version changes.

Release diagrams

These diagrams are loaded directly from README assets published with the 1.11.0 release and pinned to its immutable commit. They describe this manual’s released structure and runtime flows, not later Snapshot changes. Select a preview to open the SVG at the same release commit.