jabrena Java Functional Exception handling Best Practices
Identify and apply functional exception handling best practices in Java to improve error clarity, maintainability, and performance by eliminating exception overuse in favour of monadic error types.
What is covered in this Skill?
Optional<T>for nullable values over throwingNullPointerExceptionorNotFoundException- VAVR
Either<L,R>for predictable business-logic failures CompletableFuture<T>for async error handling- Sealed classes and records for rich error type hierarchies with exhaustive pattern matching
- Enum-based error types for simple failure cases
- Functional composition:
flatMap/map/peek/peekLeftfor chaining operations that can fail - Structured logging: warn/info for business failures, error for system failures
- Checked vs unchecked exception discipline
- Exception chaining with full causal context when exceptions are unavoidable
Scope: The reference is organized by examples (good/bad code patterns) for each core area. Apply recommendations based on applicable examples.
Constraints
Before applying any functional exception handling changes, ensure the project validates. When introducing Either types, confirm the VAVR dependency (io.vavr:vavr) and SLF4J are present.
- MANDATORY: Run
./mvnw validateormvn validatebefore applying any changes - SAFETY: If validation fails, stop immediately — do not proceed until the project is in a valid state
- DEPENDENCY: When introducing
Eithertypes, confirm VAVR (io.vavr:vavr) and SLF4J are present - VERIFY: Run
./mvnw clean verifyormvn clean verifyafter applying improvements - BEFORE APPLYING: Read the reference for detailed good/bad examples, constraints, and safeguards for each functional exception handling pattern
When to use this skill
- Review Java code for functional exception handling
- Apply best practices for functional exception handling in Java code
Reference
For detailed guidance, examples, and constraints, see references/143-java-functional-exception-handling.md.