In functional programming, the Either monad serves a special purpose: it encapsulates a value that can be one of two types, traditionally called Left and Right. The Left represents an error state or failure, while the Right represents success. We already have an Option that kind of says whether the value exists or not. However, that may not be enough all the time as it may be necessary to tell why the values are not there. Let us take a look at a simple example: we have a UserRepository - component responsible for user-related CRUD operations. Let’s imagine that we need an operation for retrieving the user by ID. I will be using the LanguageExt library in for practical examples. Suppose we need a function to retrieve a user by their ID. A straightforward approach might look like this: C# public User FindFromCache(string userId) => database.GetUser(userId); But what happens if the user does not exist in the database? To address this, we might initially consider using the Option monad: public Option<User> FindFromCache(string userId)=>
 Prelude.Option(database.GetUser(userId)); But what happens if data throws an exception? So, this is where the Either monad comes into play, providing a solution for error handling: public Either<RepositoryFailure, User> FindFromRepository(string userId) => 
        Prelude.Try(() => database
            .GetUser(userId))
            .ToEither()
            .MapLeft(f => UserFailure.DatabaseFailure(f)); In this approach, FindFromRepository can now return either a User object or a detailed error encapsulated in RepositoryFailure. This not only makes our error handling more intentional but also allows us to propagate error information across different layers of the service. To support this, we define error-handling classes and helper classes as follows: public class Database
    {
        public User GetUser(string userId) => new("3", "name");
    }

    public record User(string Id, string Name) { }

    public static class UserFailure
    {
        public static RepositryFailure Fetch(Error error) => new RepositryFailure.Fetch(error);
        public static RepositryFailure DatabaseFailure(Error error) => new RepositryFailure.DatabaseFailure(error);
        public static BusinessLogicFailure ObjectNotFound(Error error) => new BusinessLogicFailure.ObjectNotFound(error);
    }

    public abstract class RepositryFailure
    {
        public Error Error { get; }
        public RepositryFailure(Error error) => Error = error;
        public class Fetch : RepositryFailure { public Fetch(Error error) : base(error) { } }
        public class DatabaseFailure : RepositryFailure { public DatabaseFailure(Error error) : base(error) { } }
        public class ObjectNotFound : RepositryFailure { public ObjectNotFound(Error error) : base(error) { } }
    }
    public abstract class BusinessLogicFailure
    {
        public Error Error { get; }
        public BusinessLogicFailure(Error error) => Error = error;
        public class ObjectNotFound : BusinessLogicFailure { public ObjectNotFound(Error error) : base(error) { } }
    } The code can be found here https://github.com/jevgenimarenkov/language-ext-tutorials/blob/main/Either/UserRepository.cs

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

Either Monad: A Functional Approach to Error Handling in C#.

Too Long; Didn't Read

Jevgeni Marenkov

STORY’S CREDIBILITY

Guide

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Either Monad: A Functional Approach to Error Handling in C#.

Too Long; Didn't Read

Jevgeni Marenkov

STORY’S CREDIBILITY

Guide

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES