Cloud Cover Episode 43 - Scalable Counters with Windows Azure

Sign in to queue

Description

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 instancesas well as multiple threadsall 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

Embed

Download

Download this episode

The Discussion

  • User profile image
    davewill

    Apathy Button - PERFECT!  Its like an electronic stress ball.

  • User profile image
    gbrayut

    Marginally decent show  Tongue Out

    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!

  • User profile image
    MikeInOhio

    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?

  • User profile image
    Mark Tucker

    Steve & Wade care, so we don't have to.

    Thanks for the episode.

  • User profile image
    Scott

    Thanks for this! Any recommendations for how to do this in Azure Functions? What would you use to compose the ID fields?

Add Your 2 Cents