Book Image

Hands-On Azure for Developers

By : Kamil Mrzygłód
Book Image

Hands-On Azure for Developers

By: Kamil Mrzygłód

Overview of this book

Microsoft Azure is one of the fastest growing public cloud service providers in the market currently, and also holds the second highest market share after AWS. Azure has a sophisticated set of services that will help you build fault-tolerant and scalable cloud-based applications. Hands-On Azure for Developers will take you on a journey through multiple PaaS services available in Azure, including App Services, Functions, and Service Fabric, and explain in detail how to build a complete and reliable system with ease. You will learn about how to maximize your skills when building cloud-based solutions leveraging different SQL/NoSQL databases, serverless and messaging components, and even search engines such as Azure Search. In the concluding chapters, this book covers more advanced scenarios such as scalability best practices, serving static content with Azure CDN, and distributing loads with Azure Traffic Manager. By the end of the book, you will be able to build modern applications on the Azure cloud using the most popular and promising technologies, which will help make your solutions reliable, stable, and efficient.
Table of Contents (24 chapters)

Chapter 14: Enterprise Integration – Azure Service Bus

  1. In queue, once a message is read, it will not be sent to another reader. A topic allows you to implement multiple readers that are focused on the same set of messages.
  2. No, you have to use at least the Standard tier to use topics.
  3. Dead letter queue is used to avoid blocking your queue by an invalid message.
  4. In Azure Service Bus, sessions are used to ensure the FIFO message processing.
  5. The maximum size of a queue with partitioning is 80 GBs.
  6. In the active replication, you are sending a message to both namespaces. In the passive model, you send a message to the secondary namespace, but only if it can be delivered to the primary one.
  7. You have to define the primary and secondary regions, pair them, and define a trigger for failover.