Book Image

Azure for Developers. - Second Edition

By : Kamil Mrzygłód
Book Image

Azure for Developers. - Second Edition

By: Kamil Mrzygłód

Overview of this book

Microsoft Azure is currently one of the fastest growing public cloud service providers thanks to its sophisticated set of services for building fault-tolerant and scalable cloud-based applications. This second edition of Azure for Developers will take you on a journey through the various PaaS services available in Azure, including Azure App Service, Azure Functions, and Azure SQL Databases, showing you how to build a complete and reliable system with ease. Throughout the book, you’ll discover ways to enhance your skills when building cloud-based solutions leveraging different SQL/NoSQL databases, serverless and messaging components, containerized solutions, and even search engines such as Azure Cognitive Search. That’s not all!! The book also covers more advanced scenarios such as scalability best practices, serving static content with Azure CDN, and distributing loads with Azure Traffic Manager, Azure Application Gateway, and Azure Front Door. By the end of this Azure book, you’ll be able to build modern applications on the Azure cloud using the most popular and promising technologies to make your solutions reliable, stable, and efficient.
Table of Contents (32 chapters)
1
Part 1: PaaS and Containers
8
Part 2: Serverless and Reactive Architecture
14
Part 3: Storage, Messaging, and Monitoring
22
Part 4: Performance, Scalability, and Maintainability

Advanced features of Azure Service Bus

We have already covered some of the basics of the Azure Service Bus, such as SDK, the most crucial concepts, and security considerations. Now, we will focus a little bit on more advanced use cases, such as dead lettering, performance, sessions, and transactions. All those topics are crucial when developing a reliable and important service integrating many different applications and systems. Also, remember to look at the Azure Service Bus examples in the Further reading section, as this points to a GitHub repository where you can find many different use cases and concepts when using this service.

Dead lettering

In general, dead lettering means that there are messages in a queue considered dead (because there was no receiver code logic interested in pulling them), and you have two options to proceed, as follows:

  • Delete them permanently
  • Push them to an additional queue, named a dead...