Event store concept in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an event in the event store.

Microservices

event = {"type": "UserCreated", "data": [1]

Drag options to blanks, or click blank then click option'

A[123, "Alice"]

B{"userId": 123, "name": "Alice"}

C"UserCreated"

D123

Attempts:

3 left

💡 Hint

Common Mistakes

Using a list or string instead of a dictionary for event data.

The event data should be a dictionary containing relevant details, like userId and name.

2fill in blank

medium

Complete the code to append an event to the event store.

Microservices

event_store.append([1])

Drag options to blanks, or click blank then click option'

Aevent

Bevent_store

Cevent.data

Devent.type

Attempts:

3 left

💡 Hint

Common Mistakes

Appending only event type or event data instead of the full event.

We append the whole event object to the event store, not just its type or data.

3fill in blank

hard

Fix the error in the code to read events from the event store.

Microservices

for [1] in event_store:
    print(event)

Drag options to blanks, or click blank then click option'

Aevent

Bevents

Ce

Devent_store

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different variable name in the loop and print statement.

The loop variable should be 'event' to match the print statement.

4fill in blank

hard

Fill both blanks to filter events of type 'OrderPlaced' from the event store.

Microservices

filtered_events = [event for event in event_store if event[1] [2] 'OrderPlaced']

Drag options to blanks, or click blank then click option'

A.type

B==

C!=

D.data

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' instead of '==' or accessing wrong attribute.

We access the event's type attribute and check if it equals 'OrderPlaced'.

5fill in blank

hard

Fill all three blanks to create a dictionary of event counts by type.

Microservices

event_counts = [1](event.type for event in event_store if event.type[2] [3])

Drag options to blanks, or click blank then click option'

ACounter

B!=

C'UserDeleted'

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' instead of '!=' for filtering, or missing Counter import.

We use Counter to count event types, filtering out 'UserDeleted' events.

Practice

1. What is the primary purpose of an event store in a microservices architecture?

easy

A. To save every change as an immutable event in order

B. To store user credentials securely

C. To cache frequently accessed data for faster reads

D. To manage service discovery and load balancing

Solution

1. Step 1: Understand event store role

   An event store records all changes as events, preserving order and immutability.

2. Step 2: Compare options with event store purpose

   Only To save every change as an immutable event in order describes saving changes as immutable events in order, which matches event store's main function.

3. Final Answer:

   To save every change as an immutable event in order -> Option A

4. Quick Check:

   Event store = immutable ordered events [OK]

Hint: Event store saves changes as events, not data or cache [OK]

Common Mistakes:

• Confusing event store with caching layer
• Thinking event store manages security or load balancing
• Assuming event store modifies events after saving

2. Which of the following best describes the structure of data in an event store?

easy

A. A mutable key-value store with random access

B. An append-only log of immutable events

C. A relational database with tables and joins

D. A cache with time-to-live expiration

Solution

1. Step 1: Identify event store data structure

   Event stores keep data as an append-only log where events cannot be changed once stored.

2. Step 2: Match options to event store structure

   An append-only log of immutable events correctly describes an append-only log of immutable events, unlike mutable stores or caches.

3. Final Answer:

   An append-only log of immutable events -> Option B

4. Quick Check:

   Event store = append-only immutable log [OK]

Hint: Event store data is append-only and immutable, not mutable [OK]

Common Mistakes:

• Thinking event store allows event updates
• Confusing event store with relational databases
• Assuming event store is a cache with expiration

3. Given the following sequence of events stored in an event store:

1: UserCreated {userId: 1, name: "Alice"}
2: UserNameUpdated {userId: 1, name: "Alicia"}
3: UserDeleted {userId: 1}

What is the current state of the user with userId=1 after replaying these events?

medium

A. User with name "Alice" and deleted flag true

B. User with name "Alicia" exists

C. User with name "Alice" exists

D. User does not exist

Solution

1. Step 1: Replay events in order

   First event creates user Alice, second updates name to Alicia, third deletes the user.

2. Step 2: Determine final user state

   After deletion event, user no longer exists regardless of previous name changes.

3. Final Answer:

   User does not exist -> Option D

4. Quick Check:

   Last event is deletion, so user is gone [OK]

Hint: Last event determines existence; deletion means no user [OK]

Common Mistakes:

• Ignoring the delete event
• Assuming user name remains after deletion
• Confusing event replay order

4. You notice that your event store is allowing events to be updated after they are stored. What is the main issue with this behavior?

medium

A. It enables faster event replay by skipping old events

B. It improves performance by reducing storage needs

C. It breaks the immutability principle, causing inconsistent system state

D. It allows easier debugging by fixing event data

Solution

1. Step 1: Understand immutability in event stores

   Events must be immutable to ensure reliable replay and audit trails.

2. Step 2: Analyze impact of updating events

   Updating events breaks immutability, leading to inconsistent or incorrect system state.

3. Final Answer:

   It breaks the immutability principle, causing inconsistent system state -> Option C

4. Quick Check:

   Event immutability = consistent state [OK]

Hint: Events must never change after storing [OK]

Common Mistakes:

• Thinking event updates improve debugging
• Assuming updates improve performance
• Believing updates speed up replay

5. In a microservices system using an event store, how can you efficiently rebuild the current state of a service that has millions of events without replaying all events every time?

hard

A. Use snapshots to save intermediate states periodically

B. Delete old events after a certain time to reduce replay

C. Store only the latest event per entity to minimize data

D. Replay events in parallel without ordering

Solution

1. Step 1: Identify replay challenges with many events

   Replaying millions of events is slow and inefficient for rebuilding state.

2. Step 2: Evaluate solutions to speed up rebuilding

   Snapshots save the state at points in time, allowing replay from snapshot forward, reducing events to process.

3. Final Answer:

   Use snapshots to save intermediate states periodically -> Option A

4. Quick Check:

   Snapshots optimize replay by reducing event count [OK]

Hint: Snapshots speed up state rebuild, don't delete events [OK]

Common Mistakes:

• Deleting old events breaks audit and consistency
• Storing only latest event loses history
• Replaying events out of order causes errors