Event sourcing pattern in Kafka - Time & Space Complexity

Time Complexity: Event sourcing pattern

O(n)

Understanding Time Complexity

When using event sourcing with Kafka, we want to understand how the time to process events grows as more events happen.

We ask: How does the number of events affect the work Kafka does to rebuild state?

Scenario Under Consideration

Analyze the time complexity of the following Kafka event sourcing snippet.

// Consume events from a Kafka topic
consumer.subscribe(['user-events'])

while (true) {
  const records = consumer.poll(1000)
  for (const record of records) {
    // Apply event to rebuild user state
    userState.apply(record.value)
  }
}

This code reads events from Kafka and applies each event to update the user state.

Identify Repeating Operations

Look for repeated work in the code.

• Primary operation: Loop over all events received from Kafka.
• How many times: Once per event in the topic, continuously as new events arrive.

How Execution Grows With Input

As the number of events grows, the time to process all events grows too.

Input Size (n)	Approx. Operations
10	10 event applications
100	100 event applications
1000	1000 event applications

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

Final Time Complexity

Time Complexity: O(n)

This means the time to rebuild or update state grows linearly with the number of events.

Common Mistake

[X] Wrong: "Processing events is always constant time no matter how many events there are."

[OK] Correct: Each event must be applied, so more events mean more work, not the same amount.

Interview Connect

Understanding how event processing time grows helps you explain system behavior clearly and shows you can reason about real-world data flow.

Self-Check

"What if we stored snapshots periodically to avoid replaying all events? How would that change the time complexity?"

Practice

1. What is the main purpose of the event sourcing pattern in Kafka?

easy

A. To save every change as an event for a full history

B. To delete old data to save storage space

C. To process only the latest state without history

D. To send events only to one consumer

Solution

1. Step 1: Understand event sourcing concept

   Event sourcing means saving every change as a separate event instead of just the current state.

2. Step 2: Relate to Kafka usage

   Kafka topics store these events so consumers can read the full history and rebuild state if needed.

3. Final Answer:

   To save every change as an event for a full history -> Option A

4. Quick Check:

   Event sourcing = full history saved as events [OK]

Hint: Event sourcing always stores all changes, not just current state [OK]

Common Mistakes:

• Thinking event sourcing deletes old data
• Believing it only keeps latest state
• Assuming events go to only one consumer

2. Which Kafka component is primarily used to store events in event sourcing?

easy

A. Kafka Topic

B. Kafka Producer

C. Kafka Consumer

D. Kafka Broker

Solution

1. Step 1: Identify Kafka components roles

   Kafka Producer sends data, Consumer reads data, Broker manages servers, Topic stores data.

2. Step 2: Match storage role

   Events are stored in Kafka Topics, which keep the event log for consumers.

3. Final Answer:

   Kafka Topic -> Option A

4. Quick Check:

   Events stored in Kafka Topic [OK]

Hint: Events are stored in topics, not producers or consumers [OK]

Common Mistakes:

• Confusing producer with storage
• Thinking consumer stores events
• Mixing broker with event storage

3. Given this Kafka event stream, what will the consumer state be after processing all events?

events = [
  {"type": "create", "id": 1, "value": 10},
  {"type": "update", "id": 1, "value": 20},
  {"type": "create", "id": 2, "value": 5},
  {"type": "delete", "id": 1}
]

state = {}
for event in events:
    if event["type"] == "create" or event["type"] == "update":
        state[event["id"]] = event["value"]
    elif event["type"] == "delete":
        state.pop(event["id"], None)

print(state)

medium

A. {}

B. {"1": 20, "2": 5}

C. {"1": 10, "2": 5}

D. {"2": 5}

Solution

1. Step 1: Process each event in order

   First create id 1 with value 10, then update id 1 to 20, create id 2 with 5, then delete id 1.

2. Step 2: Determine final state

   After deletion, id 1 is removed, only id 2 with value 5 remains.

3. Final Answer:

   {"2": 5} -> Option D

4. Quick Check:

   Delete removes id 1, only id 2 left [OK]

Hint: Track events step-by-step to update state correctly [OK]

Common Mistakes:

• Forgetting the delete event removes id 1
• Confusing update with create
• Assuming old values remain after update

4. Identify the bug in this Kafka event consumer code snippet for event sourcing:

state = {}
for event in events:
    if event["type"] == "create":
        state[event["id"]] = event["value"]
    elif event["type"] == "update":
        if event["id"] in state:
            state[event["id"]] = event["value"]
    elif event["type"] == "delete":
        del state[event["id"]]

medium

A. Missing else clause for unknown event types

B. Using del without checking if id exists causes KeyError

C. Create should not overwrite existing id

D. Update should create new id if not present

Solution

1. Step 1: Analyze delete operation

   Using del without checking if the key exists can cause a KeyError if id is missing.

2. Step 2: Check other conditions

   Update correctly checks if id exists before updating; create overwrites which is allowed; else clause is optional.

3. Final Answer:

   Using del without checking if id exists causes KeyError -> Option B

4. Quick Check:

   del without check = KeyError risk [OK]

Hint: Always check key exists before deleting from dict [OK]

Common Mistakes:

• Ignoring KeyError on delete
• Thinking update must create new id
• Believing create cannot overwrite

5. You want to rebuild the current state from a Kafka topic storing events using event sourcing. Which approach is best to handle a large number of events efficiently?

hard

A. Read all events from the beginning every time to rebuild state

B. Only read the latest event for each entity from the topic

C. Use snapshots periodically and then replay only recent events

D. Delete old events from the topic to reduce size

Solution

1. Step 1: Understand rebuilding state from events

   Replaying all events from the start is slow for large data; deleting events loses history.

2. Step 2: Use snapshots to optimize

   Snapshots save a recent state, so only new events after snapshot need replay, improving efficiency.

3. Final Answer:

   Use snapshots periodically and then replay only recent events -> Option C

4. Quick Check:

   Snapshots + replay recent events = efficient rebuild [OK]

Hint: Snapshots speed up rebuilding by avoiding full replay [OK]

Common Mistakes:

• Replaying all events every time (slow)
• Deleting events loses full history
• Reading only latest event misses changes