Message scheduling is helpful when you want to postpone non-critical yet essential workloads to a later point in time. Then consumers can pick them up after peak hours. Scheduled messages can be canceled before the enqueue time. To cancel a message, you need its sequence number.
For example, you can delay email-sending tasks until midnight to save the computational capacity of consumers.
Another case is a consumer writing to an eventually consistent database. Adding a delay will help the message processor catch up with database writes made by upstream components.
https://miro.medium.com/v2/resize:fit:720/format:webp/1*6I5zP68kMCE5ZpeqXrKEgg.png
