Event sourcing with RabbitMQ - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a durable queue named 'events'.

RabbitMQ

channel.queue_declare(queue='events', durable=[1])

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

ATrue

BFalse

CNone

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using False makes the queue non-durable, risking message loss.

Setting durable=True ensures the queue survives RabbitMQ restarts, which is important for event sourcing.

2fill in blank

medium

Complete the code to publish a message to the 'events' exchange with routing key 'user.created'.

RabbitMQ

channel.basic_publish(exchange='events', routing_key=[1], body=message)

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

A'events'

B'user.updated'

C'order.created'

D'user.created'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong routing keys causes messages to be lost or misrouted.

The routing key 'user.created' directs the message to queues bound with this key, matching the event type.

3fill in blank

hard

Fix the error in the code to consume messages from the 'events' queue with manual acknowledgments.

RabbitMQ

channel.basic_consume(queue='events', on_message_callback=callback, auto_ack=[1])

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

ATrue

BNone

CFalse

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using True causes messages to be acknowledged immediately, risking loss.

Setting auto_ack=False means the consumer must manually acknowledge messages, which is safer for event sourcing.

4fill in blank

hard

Fill both blanks to declare a topic exchange named 'events' and bind the 'user_events' queue to receive all user-related events.

RabbitMQ

channel.exchange_declare(exchange='events', exchange_type=[1])
channel.queue_bind(queue='user_events', exchange='events', routing_key=[2])

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

A'topic'

B'direct'

C'user.*'

D'#'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'direct' exchange type does not support pattern matching.

A topic exchange allows routing keys with patterns like 'user.*' to match all user events.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that stores event data for events with version greater than 1.

RabbitMQ

event_data = {event['id']: event[1] for event in events if event['version'] [2] [3]

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

A['data']

B>

C1

D['payload']

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong keys or comparison operators causes incorrect filtering or data extraction.

This comprehension collects the 'payload' of events where the version is greater than 1, using the event ID as key.