Cloud Cover Episode 43 - Scalable Counters with Windows Azure
- Posted: Apr 08, 2011 at 9:00 AM
- 61,358 Views
- 4 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
Join Wade and Steve each week as they cover the Windows Azure Platform. You can follow and interact with the show @CloudCoverShow.
In this episode, Steve and Wade explain the application architecture of their latest creation—the Apathy Button. Like many other popular buttons on the Internet, the Apathy Button has to deal with the basic challenge of concurrency. This concurrency challenge arises from multiple role instances—as well as multiple threads—all trying to update the same number. In this show, you'll learn a few approaches to solving this in Windows Azure.
In the news:
Grab the source code the Apathy Button
Steve's blog post on the application
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Apathy Button - PERFECT! Its like an electronic stress ball.
Marginally decent show
Actually I was recently trying to figure out a way to do atomic increments using queues or table storage, so this gives me some good ideas. I really wanted a way that did not require proxying the requests through a web role to reduce scale-out costs, but after watching the show and seeing steve's response it looks like your approach would be best.
Thanks... can't wait to watch what is new next week at MIX!
It looks like some people could care less than they did. I've been watching the progress go up but the last time I checked it was down
37544
37668
37710
37618 <-- ???
Is the counter decrease related to caching or are you updating the code to only recording unique per site?
Steve & Wade care, so we don't have to.
Thanks for the episode.
Remove this comment
Remove this thread
close