In the Enterprise world of Microsoft Dynamics 365 Customer Engagement, we often use Azure Service Bus with custom code to manage heavy lift integrations and the queuing of incoming messages.

"Messages in queues are ordered and timestamped on arrival. Once the broker accepts the message, the message is always held durably in triple-redundant storage, spread across availability zones if the namespace is zone-enabled. Service Bus keeps messages in memory or volatile storage until client reports them as accepted." retrieved from Introduction to Azure Service Bus - Azure Service Bus | Microsoft Learn

Azure Service bus also offers the "pull mode" 

"Messages are delivered in pull mode, only delivering messages when requested. Unlike the busy-polling model of some other cloud queues, the pull operation can be long-lived and only complete once a message is available."

Azure Service Bus also has more advance features for more advanced needs including, but not limited to 

• Message sessions
• Auto-forwarding
• Dead-lettering
• Scheduled delivery
• Message Deferral
• Transactions
• Filters and actions
• Auto-delete on idle
• Duplicate detection

If you want to learn more about Azure Service Bus, Microsoft has kindly made available a ton of information on Microsoft Learn and it is all free. You can get started here Introduction to Azure Service Bus - Azure Service Bus | Microsoft Learn