Module 7: Optional & Null Safety

Target Audience

• Java developers facing NullPointerExceptions
• Backend developers writing service-layer logic
• Anyone aiming for safer, cleaner Java 8 code

---

1. Objective of This Module

By the end of this module, you will:

• Understand why Optional was introduced
• Use Optional correctly in real projects
• Replace fragile null checks with clean logic
• Avoid common Optional anti-patterns

---

2. The Problem with null

Before Java 8:

• null represented absence of value
• Led to frequent NullPointerException
• Required repetitive null checks

if(user != null && user.getAddress() != null) {
    ...
}

This code is:

• Hard to read
• Easy to break
• Error-prone

---

3. What Is Optional?

Optional<T> is:

• A container that may or may not contain a value
• A way to explicitly model absence of value
• A tool to reduce null-related bugs

Optional<String> name = Optional.of("Java");

---

4. Creating Optional Objects

of()

Optional<String> opt = Optional.of("value");

❌ Throws exception if value is null

ofNullable()

Optional<String> opt = Optional.ofNullable(value);

✔ Safe for null values

empty()

Optional<String> opt = Optional.empty();

---

5. Checking Presence

isPresent()

if(opt.isPresent()) {
    System.out.println(opt.get());
}

⚠️ Avoid overusing get()

---

ifPresent()

opt.ifPresent(System.out::println);

Cleaner and safer.

---

6. Providing Default Values

orElse()

String result = opt.orElse("default");

orElseGet()

String result = opt.orElseGet(() -> "default");

✔ Use orElseGet when default creation is expensive

---

orElseThrow()

String value = opt.orElseThrow(() -> new RuntimeException("Not found"));

---

7. Transforming Optional Values

map()

Optional<Integer> length =
    opt.map(String::length);

flatMap()

Optional<String> city =
    userOpt.flatMap(User::getAddress)
           .map(Address::getCity);

---

8. Optional in Real Projects

Recommended Usage

• Method return types
• Repository layer
• Service layer boundaries

Avoid Using Optional

• As method parameters
• As class fields
• For serialization entities

---

9. Common Optional Anti-Patterns

• Using Optional.get() everywhere
• Wrapping everything in Optional
• Returning Optional of Optional
• Using Optional in setters

---

10. Hands-On Exercises

Exercise 1

Refactor null checks using Optional.

Exercise 2

Chain Optional calls using map and flatMap.

Exercise 3

Replace null return with Optional in a repository method.

---

11. Summary

• Optional represents absence explicitly
• Reduces NullPointerExceptions
• Must be used thoughtfully

---

12. What’s Next?

➡️ Phase 3 – Advanced Concepts ➡️ Module 8: Interface Enhancements