Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

endpoint.tv - Windows Server AppFabric - Server Farm Setup

25 minutes, 50 seconds


Right click “Save as…”

You asked for it...here it is. In this episode, Byron Tardif is back to explain how you can setup Windows Server AppFabric in a server farm environment.

For more information, see the Windows Server AppFabric Developer Center on MSDN.


Follow the discussion

  • Oops, something didn't work.

    Getting subscription
    Subscribe to this conversation
  • Great video - as always!


    I've been following the CTPs and am looking forward to pushing esp. the caching part of App Fabric to our architecture this summer when the RTM is released. It's been a pleasure to work with the team on the API and meeting up with MK et all at PDC last year was also a really positive experience.


    Looking forward to more videos and talks on AppFabric.

  • Hüseyin Tüfekçilerlihuseyint Jack of all trades master of none

    At first client, you have initialized both Persistence and Monitoring to myMonitoringDB Smiley

  • Ron Jacobsrojacobs Ron Jacobs

    Nice catch... Wink

  • Web platform installer doesnt work in Windows 7 N !!

  • Ron Jacobsrojacobs Ron Jacobs

    Sure it does - I use it on Windows 7 all the time...

  • Dennis van der Steltdvdstelt Me @ Kinderdijk

    Is this it? Is this all there is to make your WF services run in a scaled out webfarm? With the race conditions on services and such that AppFabric resolved for you?

  • Ron Jacobsrojacobs Ron Jacobs

    Good observation - there is a race condition on the server farm.  We didn't discuss how it is dealt with in this episode but there is a solution provided.  When the workflow is loaded, it is locked by the server that is servicing the request.  If another server tries to load it during that time it will fail to obtain the lock.  It will buffer the message for a short time and retry periodically trying to obtain the lock.   If it can't get the lock, eventually it will return an error to the calling application.

Remove this comment

Remove this thread


Comments closed

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.