Skip to main content

How to Apply Observer Pattern in Csharp

If you've spent any time working with event-driven code, you've probably used the Observer pattern without even realizing it had a name. 

It's one of those foundational design patterns that shows up everywhere once you know what to look for — and once you understand it, keeping multiple parts of your application in sync stops feeling like a juggling act.

At a high level, the Observer pattern is about loose coupling: letting one object announce "hey, something changed" without needing to know or care who's listening. Let's break down how it works and walk through building one in C#.

What Exactly Is the Observer Pattern?

The pattern boils down to two roles: a subject and one or more observers. Whenever the subject's state changes, it automatically notifies every observer that's currently paying attention.

A good real-world analogy is subscribing to a YouTube channel. 

You don't have to keep refreshing the page to check for new uploads — the moment the creator posts something, every subscriber gets pinged. 

That's the Observer pattern in action, just outside the context of code.

In C#, you'll run into this pattern constantly in event-driven scenarios — GUI updates, data-binding, situations where one object's change needs to ripple out to several others without those others being tightly wired together.

The Three Moving Parts

Every implementation of the Observer pattern generally breaks down into:

  1. The Subject — the thing being watched. It keeps a list of its observers and is responsible for notifying them when something changes.
  2. The Observer Interface — a contract that defines how observers get notified (typically a single method, like Update).
  3. Concrete Observers — the actual classes that implement that interface and decide what to do when they're notified.

Let's put this into actual code.

Building It Step by Step

1. Define the Observer Interface

public interface IObserver
{
    void Update(string message);
}

This is about as simple as it gets — any class that wants to "listen" just needs to implement Update. That single method is the entire contract between the subject and its observers.

2. Build the Subject

public class Subject
{
    private List<IObserver> observers = new List<IObserver>();

    public void Attach(IObserver observer)
    {
        observers.Add(observer);
    }
    
    public void Detach(IObserver observer)
    {
        observers.Remove(observer);
    }
    
    public void Notify(string message)
    {
        foreach (var observer in observers)
        {
            observer.Update(message);
        }
    }
}

Nothing fancy here — Attach adds an observer to the list, Detach removes one, and Notify loops through everyone currently subscribed and calls their Update method. This is really the engine of the whole pattern.

3. Create a Concrete Observer

public class ConcreteObserver : IObserver
{
    private string _name;

    public ConcreteObserver(string name)
    {
        _name = name;
    }

    public void Update(string message)
    {
        Console.WriteLine($"Observer {_name} received message: {message}");
    }
}

This observer just prints out whatever message it receives, tagged with its own name — enough to demonstrate that each observer is getting notified independently.

4. Wire It All Together

class Program
{
    static void Main(string[] args)
    {
        Subject subject = new Subject();
        
        var observer1 = new ConcreteObserver("A");
        var observer2 = new ConcreteObserver("B");

        subject.Attach(observer1);
        subject.Attach(observer2);

        subject.Notify("Hello, Observers!");
        subject.Detach(observer1);
        subject.Notify("Update after detaching Observer A");
    }
}

Run this and you'll see both observers get the first message, but only Observer B gets the second one — since we detached Observer A in between. This is exactly the kind of dynamic subscribe/unsubscribe behavior that makes the pattern so useful in real applications.

5. The C# Shortcut: Using Built-In Events

Writing your own Subject/Observer plumbing is a great way to learn the pattern, but honestly, C# already gives you a cleaner way to do the same thing with its native event system:

public class SubjectWithEvent
{
    public event Action<string>? OnNotify;

    public void Notify(string message)
    {
        OnNotify?.Invoke(message);
    }
}

class ProgramWithEvents
{
    static void Main()
    {
        var subject = new SubjectWithEvent();
        
        subject.OnNotify += (message) => Console.WriteLine($"Observer 1 received message: {message}");
        subject.OnNotify += (message) => Console.WriteLine($"Observer 2 received message: {message}");

        subject.Notify("Event-driven Notification!");
    }
}

Instead of manually managing a list of observers, you're just subscribing lambda expressions (or method references) directly to an event delegate. 

Less boilerplate, same underlying idea — the event keyword is essentially doing the Attach/Notify work for you behind the scenes.

Why Bother With This Pattern?

The biggest win is loose coupling. 

Your subject doesn't need to know anything about the internal details of its observers — it just needs to know they exist and how to notify them. 

That separation makes your code a lot easier to extend, test, and debug down the line, since you can add or remove observers without touching the subject's logic at all.

And in C# specifically, the built-in event system means you get most of this benefit without writing much of the scaffolding yourself.

Labels:

Popular posts from this blog

How to Check if Someone is Connected to Your Machine in Linux

Picture this: you glance at your system monitor and notice your CPU is humming along even though you're not running anything demanding. Or maybe your internet feels sluggish for no obvious reason. A small, uneasy thought creeps in — is someone else on my machine right now? For Linux users, this isn't something you have to wonder about. Linux ships with a powerful set of built-in tools that let you see exactly who's connected, who's logged in, and what your network is doing at any given moment. You don't need to be a security expert to use them — you just need to know where to look. This guide walks you through the practical, no-nonsense steps to check for unauthorized connections on your Linux system, with real commands you can run right now. Why Monitoring Network Connections Matters Every device on a network — including your own Linux machine — communicates using an IP address. When another device or user connects to your system, that connection shows up as a trac...
Read more

How to Set Up a Linux Web Server and Host an HTML Page Easily

Setting up a web server on Linux means spending a fair amount of time in the terminal — Linux leans heavily on the command line rather than clicking through menus, so you'll be typing out instructions more often than not.  If you're new to this, it can feel a little intimidating at first, but the good news is you don't need to become a Linux wizard overnight. A handful of core commands will get you surprisingly far. A few you'll lean on constantly: cd — move between directories ls — see what's in the current directory mkdir — create a new folder nano or vim — edit files right there in the terminal sudo — run something with administrator privileges Get comfortable with these and you'll be able to navigate around, tweak configuration files, and install software without much trouble. You don't need to memorize everything — you just need to be confident enough to follow along with clear instructions, which is exactly what this guide aims to give you....
Read more

Linux Network Troubleshooting

If you've spent any time as a sysadmin — or honestly, just as someone who's had to fix their own home network at 11pm — you know that connectivity issues are one of the most common headaches out there. The good news is that a handful of core tools and a methodical approach can take you from "why isn't this working" to a root cause pretty quickly.  This guide walks through the essentials: configuring interfaces, managing routes, and diagnosing problems when things go sideways. Configuring Network Interfaces Your network interfaces are the actual bridge between your machine and the outside world, so getting them configured correctly is step one for any kind of reliable connectivity. Doing It Manually ifconfig is the old-school, tried-and-true tool for this on Unix-like systems. To see everything currently configured, run: ifconfig -a If you need to manually set up a specific interface — assigning an IP, a netmask, and bringing it online — it looks like this: ifconf...
Read more