Windows Azure Guidance – Yet another way of writing records to store and dealing with failures

These series of posts dealt with various aspects of dealing with failures while saving information on Windows Azure Storage: Windows Azure Guidance – Additional notes on failure recovery on Windows Azure Windows Azure Guidance – Failure recovery and data consistency – Part II Windows Azure Guidance – Failure recovery – Part III (Small tweak, great…


Windows Azure Guidance – Failure recovery – Part III (Small tweak, great benefits)

In the previous post, my question was about a small change in the code that would yield a big improvement. The answer is:   What changed? No try / catch We reversed the order of writes: first we write the details, then we write the “header” or “master” record for the expense. If the last…

4

Windows Azure Guidance – Failure recovery and data consistency – Part II

I had some great answers on my previous post question, like Simone’s. Some where closer than others, but in general you got it right, Thanks! The recovery strategy depicted there assumes that all failures are external. That is, writing to a table fails, for example, and you have a chance to run the clean up…

2

Windows Azure Guidance – Additional notes on failure recovery on Windows Azure

Things will eventually fail in your application and you need to be prepared. So most components should be designed for something going wrong and recover gracefully (or as gracefully as possible) and leaving the system in a consistent state (eventually in some cases). In this post I wrote about dealing with data consistency when interacting…

1

Continuation Tokens in Windows Azure Tables – Back and Previous paging

Scott has published the results of his “Continuation Token” spike, which is a critical aspect of dealing with queries against Windows Azure tables storage. His findings will make it to the guide, but you can read the essentials here. The unusual thing that you’ll see in his article is that it shows a way of…


Windows Azure Guidance – Background Processing III (creating files for another system)

Last week Scott walked me through his current design for the “Integration Service” in our sample. Here’s some preview of this early thinking. As a reminder, our fictitious scenario has a process that runs every once in a while and generates flat files for some other system to process: it simply scans the database for…

1

Windows Azure Guidance – Replacing the data tier with Azure Table Storage

This new release focuses primarily on replacing the data tier with Azure Table Storage. To make things more interesting, we changed the data model in a-Expense so it now requires two different related entities: the expense report “header” (or master) and the details (or line items) associated with it. The implementation of this on SQL…

1