Cloud Architecture Patterns on Azure with North Shore .NET User Group

Last week on Wednesday I went to hang out with a bunch of nice folks in Ipswich, MA at the 2nd meeting of the North Shore .NET User Group. It was an especially fun group with beer served before the talk! ūüôā

I spoke about Cloud Architecture Patterns like sharding, NoSQL, queue-based compute separation for scalability and reliability – with specific examples from the Windows Azure Platform such as SQL Azure Federations, Azure Table Storage, and Web Role + Queue + Worker Role patterns. The slides from my talk are here: nsnug-big-ideas-in-software-architecture-bill-wilder-14-dec-2011. (UPDATE: Note that I don’t seem to have the exact deck I used for the talk. As Ryan CrawCour pointed¬†out, the deck I posted claims that SQL Azure is limited to 50 GB and Federations has not yet shipped, but at the talk I am certain I presented the 150 GB limit and a recently released Federations. I think I made the changes on the train¬†en route to the event¬†and somehow didn’t save them. Sorry! We’ll need to live with this small skew. Post a comment here if there are questions…)

There was definitely some good discussion and¬†many questions. In fact, the following question came up, and I didn’t have a great response, but turns out there’s a timely response from Mr. SQL Azure Federations himself:

Also hope to see some nsnug folks at future Boston Azure User Group meetings and our planned Boston Azure Bootcamp in June 2012!

1 thought on “Cloud Architecture Patterns on Azure with North Shore .NET User Group

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.