Exception Hierarchy Design

Well-designed exceptions are crucial for maintainable error handling. This article covers how to design exception hierarchies that communicate intent, enable proper handling, and integrate cleanly with Spring Boot.

📋 At a Glance

---

🎯 What You'll Learn

• Exception hierarchy design principles
• Business vs technical exceptions
• Exception context and meaningful messages
• Spring Boot integration with @ControllerAdvice
• Anti-patterns to avoid

---

Production Story: The Generic Exception Disaster

A payment system used generic exceptions everywhere:

JAVA(17 lines)
Code
Loading syntax highlighter...

• No way to distinguish recoverable vs fatal errors
• Lost original cause and context
• Generic error messages to users
• No specific logging or metrics
• Impossible to retry appropriately

JAVA(26 lines)
Code
Loading syntax highlighter...

---

Mental Model: Exception Hierarchy

TEXT(28 lines)
Code
Loading syntax highlighter...

---

🔬 Deep Dive

Pattern 1: Base Exception Design

JAVA(67 lines)
Code
Loading syntax highlighter...
Show all 67 lines

---

Pattern 2: Domain-Specific Exceptions

JAVA(94 lines)
Code
Loading syntax highlighter...
Show all 94 lines

---

Pattern 3: Validation Exceptions

JAVA(54 lines)
Code
Loading syntax highlighter...
Show all 54 lines

---

Pattern 4: Technical Exceptions

JAVA(46 lines)
Code
Loading syntax highlighter...
Show all 46 lines

---

Pattern 5: Spring Boot Integration

JAVA(122 lines)
Code
Loading syntax highlighter...
Show all 122 lines

---

Pattern 6: Exception Factory

JAVA(43 lines)
Code
Loading syntax highlighter...
Show all 43 lines

---

⚠️ Common Mistakes

Mistake 1: Catching and Swallowing

JAVA(22 lines)
Code
Loading syntax highlighter...

Mistake 2: Generic Exceptions

JAVA(7 lines)
Code
Loading syntax highlighter...

Mistake 3: Exception for Flow Control

JAVA(14 lines)
Code
Loading syntax highlighter...

---

🐛 Debug This: The Swallowed Exception

A developer reports: "Orders randomly disappear after checkout! The user sees 'Order placed successfully' but no order is created."

JAVA(34 lines)
Code
Loading syntax highlighter...

---

Three critical problems:

1. Exception swallowed - The catch block logs but doesn't rethrow, so the transaction commits
2. No rollback trigger - @Transactional only rolls back on uncaught exceptions (by default RuntimeException)
3. Misleading return - User gets success message even when checkout partially failed

JAVA(34 lines)
Code
Loading syntax highlighter...

---

💻 Exercises

Exercise 1: Design Exception Hierarchy

⭐ Difficulty: Easy | ⏱️ Time: 15 minutes

JAVA(8 lines)
Code
Loading syntax highlighter...

JAVA(77 lines)
Code
Loading syntax highlighter...
Show all 77 lines

---

Exercise 2: Exception Handler

⭐⭐ Difficulty: Medium | ⏱️ Time: 20 minutes

JAVA(5 lines)
Code
Loading syntax highlighter...

JAVA(100 lines)
Code
Loading syntax highlighter...
Show all 100 lines

---

Exercise 3: Exception with Context

⭐⭐ Difficulty: Medium | ⏱️ Time: 15 minutes

JAVA(6 lines)
Code
Loading syntax highlighter...

JAVA(84 lines)
Code
Loading syntax highlighter...
Show all 84 lines

---

Exercise 4: Exception Factory

⭐⭐⭐ Difficulty: Medium-Hard | ⏱️ Time: 20 minutes

JAVA(5 lines)
Code
Loading syntax highlighter...

JAVA(91 lines)
Code
Loading syntax highlighter...
Show all 91 lines

---

Exercise 5: Transactional Exception Handling

⭐⭐⭐⭐ Difficulty: Hard | ⏱️ Time: 25 minutes

JAVA(7 lines)
Code
Loading syntax highlighter...

JAVA(121 lines)
Code
Loading syntax highlighter...
Show all 121 lines

---

🎤 Interview Questions

Q1: Checked vs Unchecked exceptions - when to use each?

• Checked: Recoverable conditions, caller CAN and SHOULD handle (IOException, SQLException)
• Unchecked: Programming errors or unrecoverable (NullPointerException, IllegalArgumentException)

Modern practice: Prefer unchecked for most cases, as checked exceptions:

• Clutter method signatures
• Often caught and wrapped anyway
• Don't work with lambdas/streams

Q2: How do you design exception hierarchy for an application?

1. Create base ApplicationException with common fields (code, context, timestamp)
2. Split into BusinessException (4xx, user-facing) and TechnicalException (5xx, logged)
3. Create domain-specific exceptions (OrderException, PaymentException)
4. Use factory methods for consistent creation
5. Integrate with global handler for uniform API responses

---

📝 Summary

---

📅 Review Schedule for This Article

---