Bird
Raised Fist0
HLDsystem_design~10 mins

Event sourcing in HLD - Interactive Code Practice

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to identify the main component that stores all changes as events.

HLD
The core component in event sourcing that stores all changes is called the [1].
Drag options to blanks, or click blank then click option'
ADatabase
BEvent Store
CCache
DLoad Balancer
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing the event store with a regular database.
Thinking the cache stores all events.
2fill in blank
medium

Complete the code to describe the process that rebuilds the current state from events.

HLD
To get the current state, event sourcing uses a process called [1] which replays all events.
Drag options to blanks, or click blank then click option'
AEvent Replay
BSnapshotting
CCaching
DLoad Balancing
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing snapshotting with event replay.
Thinking caching rebuilds the state.
3fill in blank
hard

Fix the error in the description of the event sourcing write process.

HLD
When a change happens, the system [1] the new state directly to the database.
Drag options to blanks, or click blank then click option'
Awrites
Bdeletes
Cstores events
Dcaches
Attempts:
3 left
💡 Hint
Common Mistakes
Assuming the system writes the new state directly.
Confusing storing events with caching.
4fill in blank
hard

Fill both blanks to complete the event sourcing pattern description.

HLD
In event sourcing, the [1] records all changes as events, and the [2] rebuilds the current state by applying these events.
Drag options to blanks, or click blank then click option'
AEvent Store
BCache
CEvent Processor
DLoad Balancer
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing up the roles of event store and event processor.
Choosing cache or load balancer incorrectly.
5fill in blank
hard

Fill all three blanks to complete the event sourcing write flow.

HLD
When a user action occurs, the system creates an [1], stores it in the [2], and then the [3] updates the read model.
Drag options to blanks, or click blank then click option'
AEvent
BEvent Store
CEvent Processor
DCache
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing the event with the read model.
Mixing up the event store and cache roles.