endpoint.tv - Windows Server AppFabric - Server Farm Setup
- Posted: Jun 02, 2010 at 7:31 AM
- 43,581 Views
- 7 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…”
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?
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.
At first client, you have initialized both Persistence and Monitoring to myMonitoringDB
Nice catch...
Web platform installer doesnt work in Windows 7 N !!
Sure it does - I use it on Windows 7 all the time...
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?
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
close