Event sourcing with RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is event sourcing in the context of RabbitMQ?

Event sourcing is a pattern where all changes to application state are stored as a sequence of events. RabbitMQ can be used to publish and store these events reliably for later processing or replay.

beginner

How does RabbitMQ help in implementing event sourcing?

RabbitMQ acts as a message broker that stores and forwards event messages. It ensures events are delivered to consumers in order and can persist events until they are processed.

beginner

What is a 'queue' in RabbitMQ and why is it important for event sourcing?

A queue is a buffer that stores messages (events) until consumers receive them. It ensures events are not lost and can be processed asynchronously, which is key for event sourcing reliability.

intermediate

What does 'message durability' mean in RabbitMQ and why is it important for event sourcing?

Message durability means messages are saved to disk so they survive broker restarts. This is important in event sourcing to avoid losing event data.

intermediate

What is the role of exchanges in RabbitMQ for event sourcing?

Exchanges receive messages from producers and route them to queues based on rules. They help organize how events are distributed to different parts of the system.

What does event sourcing primarily store in RabbitMQ?

A A sequence of events representing state changes

B Only the current state of the system

C User login credentials

D Database backups

Event sourcing stores all changes as a sequence of events, not just the current state.

Which RabbitMQ component routes messages to queues?

A Producer

B Queue

C Exchange

D Consumer

Exchanges receive messages from producers and route them to queues.

Why is message durability important in event sourcing with RabbitMQ?

A To speed up message delivery

B To prevent losing events if RabbitMQ restarts

C To encrypt messages

D To limit message size

Durability ensures messages survive broker restarts, preventing event loss.

What is a queue in RabbitMQ?

A A tool to create messages

B A type of exchange

C A user interface for RabbitMQ

D A storage for messages until consumers process them

Queues store messages until consumers receive and process them.

In event sourcing, why might you replay events from RabbitMQ?

A To rebuild the current state from past events

B To delete old messages

C To speed up message delivery

D To encrypt messages

Replaying events helps reconstruct the system state by applying all past changes.

Explain how RabbitMQ supports the event sourcing pattern in an application.

Think about how events flow from producers to consumers and how RabbitMQ keeps them safe.

Describe the importance of message durability and queues in RabbitMQ when implementing event sourcing.

Consider what happens if RabbitMQ restarts or consumers are slow.

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