Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Robust Cloud Integration with Azure

You're reading from  Robust Cloud Integration with Azure

Product type Book
Published in Mar 2017
Publisher Packt
ISBN-13 9781786465573
Pages 696 pages
Edition 1st Edition
Languages
Authors (6):
Gyanendra Kumar Gautam Gyanendra Kumar Gautam
Ashish Bhambhani Ashish Bhambhani
Profile icon Ashish Bhambhani
Abhishek Kumar Abhishek Kumar
Profile icon Abhishek Kumar
James Corbould James Corbould
Profile icon James Corbould
Mahindra Morar Mahindra Morar
Profile icon Mahindra Morar
Martin Abbott Martin Abbott
Profile icon Martin Abbott
View More author details

Table of Contents (23) Chapters

Robust Cloud Integration with Azure
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
1. An Introduction to Systems Integration in the Cloud 2. What Is an Azure App Service? 3. Getting Started with API Apps 4. What is Azure API Management? 5. Trigger Your First Logic App in Azure 6. Working with Connectors in Logic Apps 7. Azure Functions in Logic Apps 8. A Deep Dive into Logic Apps 9. Powerful Integration with SaaS Using Logic Apps 10. Advanced Integration with Powerful, Scalable Service Bus in the Cloud 11. Connecting to Event Hubs and an Introduction to IoT Hubs 12. EAI/B2B Integration Using Logic Apps 13. Hybrid Integration Using BizTalk Server 2016 and Logic Apps 14. Tooling and Monitoring for Logic Apps 15. Whats Next for Azure Integration?

Deferring message processing


Deferring messages allows the processing of higher priority messages first and then servicing the lower priority messages at a later time.

To use this feature, the receive mode must set to PeekLock. The client receiving the message then has the option to mark the message as being deferred. When the client marks the message to be deferred, they must keep track of the message sequence number in a durable store to be retrieved later.

When a message has been deferred, it will stay in the queue until it is retrieved and the Complete() method has been called. The message will also be removed from the Queue if a message TTL expiry timeout occurs.

The message is read from the queue using the QueueClient class available in the Azure Service Bus SDK and passing the message sequence number that was persisted previously.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}