http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Wolf, The screen casts are below, in the download section. http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment5http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment5Sun, 25 Nov 2007 01:06:00 GMTAs a configuration manager, I am reading your posts on deployments intently. I am managing a system that has a high uptime requirement, multiple websites/webservices, scheduled console app jobs, ssis packages, and has a lot of DB schema change. I have a ways to go before we have the one step deployment scenario I dream of. Thanks for the great posts on deployment. They're giving me some good ideas to help shape my system. On my journey to worry free deployments, I went to watch your screen cast on hot code swapping. Unfortunately I couldn't find the link for the screen cast. The png on the right just links to itself. Am I missing the link, or is the link missing? Thanks! http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment4http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment4Sun, 25 Nov 2007 01:01:24 GMTMichael, Thanks, fixed. I will go and put myself in a corner until I can come up with a satisfactory answer for 2+4. Be back in an hour. http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment3http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment3Sat, 24 Nov 2007 16:25:49 GMTYour "downtime per month" table is off. 3 days downtime per month would be 10% down (90% uptime) 99% uptime = approx 7.2hrs down per month 99.9% uptime = approx 43 minutes down per month 99.99% uptime = approx 4.3 minutes down per month 99.999% = approx 26 seconds down per month http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment2http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment2Sat, 24 Nov 2007 13:33:47 GMTIf you really do have two database machines to work with as well as two application tier machines (or two vm instances) as well as a pair of load balanced web servers for the Presentation Tier, you can accomplish the database upgrades in the following manner (with some stipulations): Assuming the Presentation Tier sends messages (in one format or another) to the Application Tier, you can do this: --Start recording incoming messages from the UI --Take One Pair (App/Db) Offline --Upgrade One Pair --Playback Recorded Messages to Bring Offline Pair back up to speed (on shiny new DB schema) --Bring the Offline Pair Back Online --Take the other pair offline --Rinse and Repeat There are some caveats in this (which I won't blather on about in your comments), but it will work if done right. Evan http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment1http://ayende.com/2964/a-vision-of-enterprise-platform-hot-distributed-deployment#comment1Sat, 24 Nov 2007 01:11:53 GMT