Event sourcing with RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Event Sourcing with RabbitMQ

What is the primary role of RabbitMQ in an event sourcing architecture?

A To store the complete state of the application in a database

B To act as a message broker that transports events between services

C To execute business logic when events occur

D To replace the need for event storage entirely

💡 Hint

Think about what RabbitMQ does best in a system that uses events.

RabbitMQ is a message broker that transports events reliably between producers and consumers. It does not store the full application state or execute business logic.

💻 Command Output

intermediate

RabbitMQ Queue Declaration Output

What is the output of the following RabbitMQ CLI command?

rabbitmqctl list_queues

A Empty output with no queues listed

B Error: RabbitMQ server not running

C Syntax error: command not found

D Listing of all queues with their message counts

💡 Hint

This command lists queues and their message counts if the server is running.

The rabbitmqctl list_queues command outputs all queues with their message counts if RabbitMQ is running properly.

❓ Configuration

advanced

Configuring a Durable Queue for Event Sourcing

Which RabbitMQ queue configuration ensures that events are not lost if the broker restarts?

A queue_declare(queue='events', durable=False)

B queue_declare(queue='events', exclusive=True)

C queue_declare(queue='events', durable=True)

D queue_declare(queue='events', auto_delete=True)

💡 Hint

Durability means the queue survives broker restarts.

Setting durable=True makes the queue survive RabbitMQ restarts, which is critical for event sourcing to avoid losing events.

🔀 Workflow

advanced

Event Publishing and Consumption Workflow

In an event sourcing system using RabbitMQ, what is the correct order of steps when a new event is generated?

A 2,1,3,4

B 1,3,4,2

C 1,2,3,4

D 2,3,1,4

💡 Hint

Think about storing the event before publishing it.

In event sourcing, the event is first stored in the event store, then published to RabbitMQ exchange, routed to queues, and finally consumed.

❓ Troubleshoot

expert

Diagnosing Missing Events in RabbitMQ

You notice that some events are missing from your consumer application logs. Which RabbitMQ misconfiguration is the most likely cause?

A The queue is declared as non-durable and RabbitMQ was restarted.

B The exchange type is set to 'fanout'.

C The consumer is using manual acknowledgments.

D The queue has a high prefetch count.

💡 Hint

Consider what happens to non-durable queues on broker restart.

Non-durable queues are deleted when RabbitMQ restarts, causing events to be lost and missing from consumers.

Practice

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

easy

A. To record all changes as a sequence of events

B. To delete old messages automatically

C. To speed up message delivery by skipping queues

D. To encrypt messages before sending

Solution

1. Step 1: Understand event sourcing concept

   Event sourcing means storing every change as an event, not just the current state.

2. Step 2: Connect event sourcing to RabbitMQ

   RabbitMQ can store and forward these events reliably using exchanges and queues.

3. Final Answer:

   To record all changes as a sequence of events -> Option A

4. Quick Check:

   Event sourcing = record all changes as events [OK]

Hint: Event sourcing means saving every change as an event [OK]

Common Mistakes:

• Thinking event sourcing deletes old data
• Confusing event sourcing with encryption
• Assuming event sourcing skips queues

2. Which RabbitMQ component is responsible for routing events to queues based on routing keys?

easy

A. Queue

B. Binding

C. Channel

D. Exchange

Solution

1. Step 1: Identify RabbitMQ components

   Exchanges receive messages and decide where to send them using routing keys.

2. Step 2: Role of routing keys and bindings

   Bindings connect exchanges to queues, but routing decisions happen inside exchanges.

3. Final Answer:

   Exchange -> Option D

4. Quick Check:

   Routing keys route messages via exchanges [OK]

Hint: Exchanges route messages using routing keys [OK]

Common Mistakes:

• Confusing bindings as routing decision makers
• Thinking queues route messages
• Mixing channels with routing

3. Given this RabbitMQ setup:

channel.exchange_declare(exchange='events', exchange_type='direct')
channel.queue_declare(queue='order_events')
channel.queue_bind(queue='order_events', exchange='events', routing_key='order.created')
channel.basic_publish(exchange='events', routing_key='order.created', body='Order123')

What happens when the message is published?

medium

A. Message causes an error due to missing routing key

B. Message is discarded because no queue matches

C. Message is sent to 'order_events' queue

D. Message is sent to all queues bound to 'events' exchange

Solution

1. Step 1: Analyze exchange and queue binding

   The 'events' exchange is direct type, routing key 'order.created' binds to 'order_events' queue.

2. Step 2: Check message publish routing

   Message with routing key 'order.created' matches binding, so it goes to 'order_events' queue.

3. Final Answer:

   Message is sent to 'order_events' queue -> Option C

4. Quick Check:

   Direct exchange routes by exact routing key [OK]

Hint: Direct exchange sends message only to matching routing key queue [OK]

Common Mistakes:

• Assuming message goes to all queues
• Thinking message is discarded without error
• Forgetting routing key is required

4. You wrote this code to bind a queue but it doesn't receive messages:

channel.queue_bind(queue='events_queue', exchange='events_exchange', routing_key='user.updated')

What is the most likely reason messages are not received?

medium

A. The queue was not declared before binding

B. The routing key used in publishing does not match 'user.updated'

C. The exchange type does not support routing keys

D. The channel was closed before binding

Solution

1. Step 1: Verify routing key matching

   Messages only reach queues if routing keys match bindings exactly.

2. Step 2: Check publishing routing key

   If published messages use a different routing key, queue won't get them despite binding.

3. Final Answer:

   The routing key used in publishing does not match 'user.updated' -> Option B

4. Quick Check:

   Routing keys must match for delivery [OK]

Hint: Routing keys must match exactly to deliver messages [OK]

Common Mistakes:

• Assuming exchange type blocks routing keys
• Forgetting to declare queue before binding
• Not checking if channel is open

5. You want to implement event sourcing with RabbitMQ to track user actions. Which setup best ensures all user events are stored and can be replayed later?

hard

A. Use a topic exchange with queues bound by event patterns, and enable message persistence and acknowledgments

B. Use a fanout exchange to broadcast events to multiple queues, each storing events for different services

C. Use a direct exchange with one queue per event type, but do not persist messages after consumption

D. Use a headers exchange without bindings, relying on message headers only

Solution

1. Step 1: Understand event sourcing needs

   Event sourcing requires storing all events reliably and replaying them later.

2. Step 2: Evaluate exchange types and persistence

   Topic exchange allows flexible routing by event patterns; persistence and acknowledgments ensure events are saved and not lost.

3. Step 3: Compare options

   Fanout broadcasts but may not filter; direct without persistence loses events; headers without bindings is unreliable.

4. Final Answer:

   Use a topic exchange with queues bound by event patterns, and enable message persistence and acknowledgments -> Option A

5. Quick Check:

   Topic exchange + persistence = reliable event sourcing [OK]

Hint: Use topic exchange with persistence for flexible, reliable event storage [OK]

Common Mistakes:

• Ignoring message persistence
• Using fanout without filtering
• Relying on headers exchange without bindings