webflux-reactive-patterns
Use when the complete Spring Boot 3 request path is reactive: WebFlux controllers, Reactor pipelines, R2DBC persistence, streaming, backpressure, or cancellation. For defining and registering declarative outbound API interfaces, use http-interface-clients.
How do I install this agent skill?
npx skills add https://github.com/rrezartprebreza/spring-boot-skills --skill webflux-reactive-patternsIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides architectural guidelines and coding standards for building reactive applications using Spring WebFlux and Project Reactor. It includes best practices for non-blocking I/O, error handling, and testing within Spring Boot environments. No security risks or malicious patterns were identified.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
WebFlux Reactive Patterns
Use WebFlux when the complete request path can benefit from non-blocking I/O.
Pipeline rules
- Return
MonoorFlux; do not callsubscribe()in request-handling code. - Compose work with
map,flatMap,concatMap, andzipaccording to ordering requirements. - Keep blocking JDBC, filesystem, and legacy SDK calls out of event-loop threads.
- Isolate unavoidable blocking calls on
boundedElasticat the narrow adapter boundary. - Apply timeouts at remote-call boundaries and preserve cancellation.
Context and errors
- Put request-scoped metadata in Reactor
Context, notThreadLocal. - Translate domain failures centrally without swallowing cancellation or infrastructure errors.
- Use
onErrorResumeonly when a defined fallback exists. - Avoid
onErrorContinue; it makes partial processing hard to reason about.
Persistence and streaming
- Use R2DBC for reactive database access; JDBC makes the pipeline blocking.
- Bound concurrency for fan-out operations.
- Define backpressure and buffering limits for streaming endpoints.
- Avoid collecting an unbounded
Fluxinto memory.
Testing
- Use
StepVerifierfor publisher behavior andWebTestClientfor HTTP contracts. - Test cancellation, timeout, empty results, errors, ordering, and backpressure.
- Enable blocking-call detection in tests when the project supports it.
Examples
- See
examples/good-reactive-service.javaandexamples/bad-reactive-service.java.
Verification scope
The workflow fixture compiles good-reactive-service.java directly and checks found/missing results, upstream errors, virtual-time timeout and cancellation propagation. It does not verify a WebFlux HTTP server, R2DBC driver or reactive tenant context. See the coverage matrix for pinned versions and remaining gaps.
Gotchas
- Agent calls
block()in a controller or service - keep the full request path non-blocking. - Agent calls
subscribe()manually - the web runtime owns subscription. - Agent stores tenant or security data in
ThreadLocal- use ReactorContext. - Agent uses unbounded
flatMap- set concurrency according to downstream capacity. - Agent wraps JDBC in
Mono.just- that still blocks the caller thread.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/rrezartprebreza/spring-boot-skills/webflux-reactive-patterns">View webflux-reactive-patterns on skillZs</a>