Course contentsShow
← Java
Lesson 1815 of 2,87037. Optional for Null SafetyFree lesson

Combining or with map and flatMap

Use or() within transformation pipelines to provide default Optional values after mapping operations.

Combining or with map and flatMap

You'll learn how to build robust transformation pipelines by combining or() with map() and flatMap() to handle fallback logic at any stage.

The Pattern: Transform Then Provide Alternatives

You've seen how map() and flatMap() transform Optional values, and how or() provides alternative Optionals when empty. The real power emerges when you combine them: transform an Optional, and if the transformation produces nothing, fall back to another Optional source.

This pattern is incredibly useful when you have multiple potential sources for a value, each requiring different transformations or access logic.

Basic Combination: Transform with Fallback

Optional<String> primary = Optional.of("user123");
Optional<String> backup = Optional.of("guest");

// Transform primary, fall back to backup if transformation yields empty
Optional<String> result = primary
    .map(id -> findUserName(id))  // Returns Optional<String>
    .flatMap(Function.identity())  // Flatten nested Optional
    .or(() -> backup);

More Practical: Multi-Stage Fallback Chain

Optional<Config> userConfig = getUserConfig();
Optional<Config> teamConfig = getTeamConfig();
Optional<Config> defaultConfig = getDefaultConfig();

Optional<String> setting = userConfig
    .flatMap(c -> c.getSetting("theme"))  // Try user config
    .or(() -> teamConfig.flatMap(c -> c.getSetting("theme")))  // Try team
    .or(() -> defaultConfig.flatMap(c -> c.getSetting("theme")));  // Default

Why This Matters

Think of it like searching for your keys: check your jacket pocket (transform by looking), if not there, check your bag (fallback Optional), if not there, check the key hook. Each location might require a different "search method" (transformation).

The or() method lets you defer to alternative Optional pipelines, keeping your entire chain fluent and null-safe without unwrapping prematurely.

Key Takeaway: Use or() after map() or flatMap() to build resilient transformation pipelines that gracefully fall back to alternative Optional sources when earlier transformations produce empty results.