Guaranteed delivery: A message will be indefinitely retried until a successful ack is received. • Non-blocking: If the sending is backlogged, new messages continue to be accepted for eventual delivery. • Adaptive: Adaptive: Messages that fail delivery are backed off exponentially. • Analytics: The retention period for messages is dictated by the application. One could potentially choose to never delete any messages Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are not a good fit for

Guaranteed delivery: A message will be indefinitely retried until a successful ack is received. • Non-blocking: If the sending is backlogged, new messages continue to be accepted for eventual delivery. 88 • Adaptive: Messages that fail delivery are backed off exponentially. • Analytics: The retention period for messages is dictated by the application. One could potentially choose to never delete any messages Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are not a good fit for

Guaranteed delivery: A message will be indefinitely retried until a successful ack is received. • Non-blocking: If the sending is backlogged, new messages continue to be accepted for eventual delivery. • Adaptive: Adaptive: Messages that fail delivery are backed off exponentially. • Analytics: The retention period for messages is dictated by the application. One could potentially choose to never delete any messages Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are not a good fit for

Guaranteed delivery: A message will be indefinitely retried until a successful ack is received. • Non-blocking: If the sending is backlogged, new messages continue to be accepted for eventual delivery. • Adaptive: Adaptive: Messages that fail delivery are backed off exponentially. • Analytics: The retention period for messages is dictated by the application. One could potentially choose to never delete any messages Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. 98 • Accumulating work that could be done during off-peak hours. Messages are not a good fit

Guaranteed delivery: A message will be indefinitely retried until a successful ack is received. • Non-blocking: If the sending is backlogged, new messages continue to be accepted for eventual delivery. • Adaptive: Adaptive: Messages that fail delivery are backed off exponentially. • Analytics: The retention period for messages is dictated by the application. One could potentially choose to never delete any messages Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are not a good fit for

Guaranteed delivery: A message will be indefinitely retried until a successful ack is received. • Non-blocking: If the sending is backlogged, new messages continue to be accepted for eventual delivery. • Adaptive: Adaptive: Messages that fail delivery are backed off exponentially. • Analytics: The retention period for messages is dictated by the application. One could potentially choose to never delete any messages Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are not a good fit for

Guaranteed delivery: A message will be indefinitely retried until a successful ack is received. • Non-blocking: If the sending is backlogged, new messages continue to be accepted for eventual delivery. • Adaptive: Adaptive: Messages that fail delivery are backed off exponentially. • Analytics: The retention period for messages is dictated by the application. One could potentially choose to never delete any messages Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are not a good fit for

Guaranteed delivery: A message will be indefinitely retried until a successful ack is received. • Non-blocking: If the sending is backlogged, new messages continue to be accepted for eventual delivery. • Adaptive: Adaptive: Messages that fail delivery are backed off exponentially. • Analytics: The retention period for messages is dictated by the application. One could potentially choose to never delete any messages Recording potentially time-consuming work that needs to be done asynchronously. • Scheduling for future delivery. • Accumulating work that could be done during off-peak hours. Messages are not a good fit for

ongoing security work. For example, Ada Logics attempted to involve the project in integrating continuous fuzzing by way of OSS-Fuzz in 2020: https://github.com/gorilla/mux/pull/575 via a pull request