Event-driven design pattern in C Sharp (C#) - Time & Space Complexity

Time Complexity: Event-driven design pattern

O(n)

Understanding Time Complexity

When using the event-driven design pattern, it's important to understand how the program's work grows as more events happen.

We want to see how the number of events affects the time the program takes to respond.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

public class Publisher
{
    public event Action? OnChange;

    public void RaiseEvent()
    {
        OnChange?.Invoke();
    }
}

public class Subscriber
{
    public void Respond() { /* handle event */ }
}
    

This code shows a publisher that raises an event and subscribers that respond when the event happens.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Invoking all subscriber methods when the event is raised.
• How many times: Once per event raised, calling each subscriber's response method.

How Execution Grows With Input

Each time the event is raised, the program calls every subscriber's response method.

Input Size (n subscribers)	Approx. Operations per Event
10	10 calls
100	100 calls
1000	1000 calls

Pattern observation: The work grows directly with the number of subscribers.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle an event grows linearly with the number of subscribers listening.

Common Mistake

[X] Wrong: "Raising an event always takes the same time no matter how many subscribers there are."

[OK] Correct: Each subscriber adds work because the event calls their method, so more subscribers mean more calls and more time.

Interview Connect

Understanding how event handling scales helps you design responsive programs and shows you can think about performance in real situations.

Self-Check

"What if the event had to notify subscribers in a nested way, where each subscriber triggers another event? How would the time complexity change?"

Practice

1. What is the main role of an event subscriber in the event-driven design pattern?

easy

A. To manage the program's user interface layout

B. To listen for events and respond when they occur

C. To store data for the program's use

D. To create and send events to other parts of the program

Solution

1. Step 1: Understand the roles in event-driven design

   In event-driven design, publishers send events and subscribers listen for these events.

2. Step 2: Identify subscriber's responsibility

   The subscriber's job is to react or respond when an event happens, meaning it listens and acts accordingly.

3. Final Answer:

   To listen for events and respond when they occur -> Option B

4. Quick Check:

   Subscriber listens and reacts = D [OK]

Hint: Subscribers always listen and react to events [OK]

Common Mistakes:

• Confusing subscriber with publisher
• Thinking subscriber creates events
• Assuming subscriber manages UI layout

2. Which of the following is the correct syntax to declare an event in C#?

easy

A. public void event MyEvent();

B. event public MyEvent EventHandler;

C. public event EventHandler MyEvent;

D. EventHandler public event MyEvent;

Solution

1. Step 1: Recall event declaration syntax in C#

   Events are declared with the keyword 'event' followed by a delegate type, then the event name.

2. Step 2: Check each option

   public event EventHandler MyEvent; matches the correct syntax: 'public event EventHandler MyEvent;'. Others have wrong order or keywords.

3. Final Answer:

   public event EventHandler MyEvent; -> Option C

4. Quick Check:

   Correct event declaration = B [OK]

Hint: Event declaration: 'public event DelegateType EventName;' [OK]

Common Mistakes:

• Mixing method and event syntax
• Wrong keyword order
• Missing 'event' keyword

3. What will be the output of the following C# code?

using System;
class Program {
  public static event Action OnNotify;
  static void Main() {
    OnNotify += () => Console.WriteLine("Event triggered");
    OnNotify?.Invoke();
  }
}

medium

A. Event triggered

B. No output

C. Compilation error

D. Runtime exception

Solution

1. Step 1: Understand event subscription and invocation

   The event OnNotify is subscribed with a lambda that prints "Event triggered". The event is then invoked safely with ?.Invoke().

2. Step 2: Predict output

   Since OnNotify has a subscriber, invoking it calls the lambda, printing "Event triggered" to the console.

3. Final Answer:

   Event triggered -> Option A

4. Quick Check:

   Subscribed event invoked prints message = A [OK]

Hint: Subscribed event invocation prints output [OK]

Common Mistakes:

• Ignoring null-conditional operator ?.Invoke()
• Expecting no output without subscription
• Confusing event with method call syntax

4. Identify the error in this C# event-driven code snippet:

public class Publisher {
  public event EventHandler OnChange;
  public void Raise() {
    OnChange();
  }
}

medium

A. OnChange event is invoked without checking for null

B. EventHandler delegate is not declared

C. Raise method should be static

D. Event should be private

Solution

1. Step 1: Review event invocation rules

   Events can be null if no subscribers exist. Invoking without null check causes runtime error.

2. Step 2: Identify the error in code

   OnChange() is called directly without checking if OnChange is null, risking NullReferenceException.

3. Final Answer:

   OnChange event is invoked without checking for null -> Option A

4. Quick Check:

   Invoke event safely with null check = C [OK]

Hint: Always check event for null before invoking [OK]

Common Mistakes:

• Calling event without null check
• Assuming event is never null
• Misunderstanding event access modifiers

5. You want to design a system where multiple subscribers react differently to a button click event. Which approach best uses the event-driven pattern in C# to achieve this?

hard

A. Make subscribers poll the button state continuously in a loop

B. Create a list of methods and call them manually without events

C. Use a static method to handle all button clicks centrally

D. Declare a public event, let subscribers add their handlers, and invoke event on button click

Solution

1. Step 1: Understand event-driven design for multiple subscribers

   Events allow multiple subscribers to register handlers that get called automatically when the event fires.

2. Step 2: Evaluate options for best practice

   Declare a public event, let subscribers add their handlers, and invoke event on button click uses a public event and lets subscribers add handlers, which is the standard event-driven approach. Others are less efficient or not event-driven.

3. Final Answer:

   Declare a public event, let subscribers add their handlers, and invoke event on button click -> Option D

4. Quick Check:

   Use events for multiple subscriber reactions = A [OK]

Hint: Use events to notify multiple subscribers automatically [OK]

Common Mistakes:

• Manually calling subscriber methods instead of using events
• Using polling instead of event notifications
• Centralizing all logic in static methods