Reactive WebFlux & R2DBC — Spring Boot 3.4 Architecture Blueprint

Scaffold production-ready Reactive WebFlux & R2DBC for Spring Boot 3.4: Asynchronous non-blocking controllers (Mono/Flux), reactive R2DBC database repository, and Netty runtime. Pre-wired JPA, starters, and Docker Compose.

Overview & Architecture Pattern

Asynchronous non-blocking controllers (Mono/Flux), reactive R2DBC database repository, and Netty runtime.

Architecture Pattern: Web & Reactive

Primary Use Case: High-concurrency streaming APIs, Server-Sent Events (SSE), IoT telemetry data ingestion.

Included Dependencies & Starters

spring-boot-starter-webflux, spring-boot-starter-data-r2dbc, r2dbc-postgresql

Domain Entities & Scaffolding Defaults

User (id, username, email, active)

Quickstart: Running Your Project

# 1. Start required infrastructure containers
docker compose up -d

# 2. Run the Spring Boot 3.4 application (Maven)
./mvnw spring-boot:run

# Or run with Gradle
./gradlew bootRun

Frequently Asked Questions

What starters are included in the Reactive WebFlux & R2DBC blueprint?
The Reactive WebFlux & R2DBC blueprint includes spring-boot-starter-webflux, spring-boot-starter-data-r2dbc, r2dbc-postgresql, pre-configured application.yml properties, and production-ready connection pools.
How do I run the generated Reactive WebFlux & R2DBC project locally?
Extract the downloaded ZIP, start dependencies with 'docker compose up -d', and execute './mvnw spring-boot:run' (Maven) or './gradlew bootRun' (Gradle).
Can I customize entities and database schemas in this blueprint?
Yes, SpringForge allows you to visually add or modify JPA entities, field types, validation rules, and relational mappings, or import SQL DDL schemas.