Book Image

Microsoft Windows Azure Development Cookbook

By : Neil Mackenzie
Book Image

Microsoft Windows Azure Development Cookbook

By: Neil Mackenzie

Overview of this book

The Windows Azure platform is Microsoft's Platform-as-a-Service environment for hosting services and data in the cloud. It provides developers with on-demand computing, storage, and service connectivity capabilities that facilitate the hosting of highly scalable services in Windows Azure datacenters across the globe. This practical cookbook will show you advanced development techniques for building highly scalable cloud-based services using the Windows Azure platform. It contains over 80 practical, task-based, and immediately usable recipes covering a wide range of advanced development techniques for building highly scalable services to solve particular problems/scenarios when developing these services on the Windows Azure platform. Packed with reusable, real-world recipes, the book starts by explaining the various access control mechanisms used in the Windows Azure platform. Next you will see the advanced features of Windows Azure Blob storage, Windows Azure Table storage, and Windows Azure Queues. The book then dives deep into topics such as developing Windows Azure hosted services, using Windows Azure Diagnostics, managing hosted services with the Service Management API, using SQL Azure and the Windows Azure AppFabric Service Bus. You will see how to use several of the latest features such as VM roles, Windows Azure Connect, startup tasks, and the Windows Azure AppFabric Caching Service.
Table of Contents (16 chapters)
Microsoft Windows Azure Development Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Using a Service Bus message buffer


The Windows Azure AppFabric Service Bus supports disconnected communication between a client and a server through a message buffer implemented as a named endpoint on the Service Bus. A client can insert a message into a message buffer, and the server can later retrieve the message from the buffer. The server can respond to the client by putting a message in another buffer which the client can read.

By default, a message buffer may contain 10 messages, but it can be configured to hold up to 50 messages. A message buffer is transient and is automatically deleted when it has not been used for a configurable amount of time, with a default of 5 minutes and a maximum of 10 minutes. Message buffers are stored in memory and are not persisted to permanent storage. Consequently, it is possible that the contents of a message buffer are lost if the server storing it encounters a problem.

In this recipe, we will learn how to use a message buffer to implement disconnected...