We're sorry but this app doesn't work properly without JavaScript enabled. Please enable it to continue.

This lesson's interactive features are locked, please to keep using them

Durable

Durable queues survive a server restart, and in our case, we'll also make sure they:

  1. Are not deleted automatically when they are no longer in use
  2. Are not exclusive (multiple consumers can share the same queue)

Assignment

Update the cmd/server application to declare and bind a queue to the new peril_topic exchange.

Run and submit the CLI tests.

Tips

Some constants that will be useful:

  • routing.ExchangePerilTopic
  • routing.GameLogSlug