Windows Azure Architecture Guide – Part 2 – TailSpin Surveys – AuthN and AuthZ by Eugenio Pace

Tailspin Surveys is a multitenant, SaaS solution, targeting many different customers. Some of these customers might be “enterprise” with “Big-IT” and are likely to demand advanced integration capabilities for identity (e.g. identity federation). Others...

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

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...

Windows Azure Architecture Guide – Part 1 – Complete, Starting Part 2 by Eugenio Pace

We are “done” with the first part of the guide. You can download the guide release candidate from here . I want to thank the long list of reviewers and contributors for this first deliverable. Thanks much!!   Windows Azure Architecture Guide – Part...

Windows Azure Guidance – The “Get”, “Delete” pattern for reading messages from queues by Eugenio Pace

Fabio asked me on twitter “why there’re no dequeue , peek and enqueue on Windows Azure Queues?”   One of the most common patterns for interactions with queues is this:     You get the message from the queue. This is not a “dequeue”, even...

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

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...

Windows Azure Guidance – Failure recovery and data consistency – Part II by Eugenio Pace

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...

Windows Azure Guidance – New Code & Doc drop on CodePlex by Eugenio Pace

We are almost content complete for our first Windows Azure Architecture Guide (the most probable name for our book). Available for download today: New updated samples, including all file processing and background tasks (lot’s of small nuggets in there...

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

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...

Windows Azure Guidance – Background processing II – One worker, two workers, … by Eugenio Pace

Question for you: if your application has 2 “background” task to perform, do you implement this as 2 distinct workers? or as 1 worker with 2 responsibilities? Option 1 is straight forward. Option 2 requires more work, but … does it make sense? It turns...

Windows Azure Guidance – Using Shared Key Signatures for images in a-Expense by Eugenio Pace

As described before , a-Expense static content (mainly the scanned images uploaded by users) is stored in blobs. As with many other things in life there are quite a few options when it comes to how those images are made available to users. A key design...

Windows Azure Guidance – Development Process by Eugenio Pace

One frequent question we get is around “process guidance”. Also known by the more modern and fancy acronym “ALM”: A pplication L ifecycle M anagement, which replaced the old SDLC term, which in turn (and only if you are old enough like me) meant something...

Windows Azure Guidance – Replacing the data tier with Azure Table Storage by Eugenio Pace

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)...

Windows Azure Guidance – First version of a-Expense in the cloud by Eugenio Pace

Available for download here , you’ll find the first step in taking a-Expense to Windows Azure. Highlights of this release are: Use of SQL Azure as the backend store for application entities (e.g. expense reports) Uses Azure storage for user profile information...

Windows Azure Guidance – A (simplistic) economic analysis of a-Expense migration by Eugenio Pace

A big motivation for considering hosting on Windows Azure is cost. Each month, Microsoft will send Adatum a bill for the Windows Azure resources used. This is a very fast feedback loop on how they are using the infrastructure. Did I say that money is...
More Posts Next page »
Powered by Community Server (Non-Commercial Edition), by Telligent Systems