Gabriel Sechan wrote: >> From: [EMAIL PROTECTED] >> >>> Gabriel Sechan wrote: >>> Yes- I've dealt with self modifying code in asm and C. The better question- >>> why the hell would you want this? Its a maintenance and securrity >>> nightmare. >>> >> Uptime. >> >> If you have a system which simply cannot go down no matter what, you >> need hot swap. >> > > I'm still finding myself skeptic- a system that needs 100% uptime that > doesn't have physical redundancy? And if it has redundancy, why not stagger > the rollout, taking down 1 machine at a time and replacing it? > Actually, that is somewhat like how Erlang does it, except it does it at the Erlang process level, rather than the machine level. The advantage to that being that you typically have thousands of Erlang processes, so losing a few of them during a transition isn't so much of a problem. Losing entire machines means that you essentially have to pad your hardware budget significantly (unless you are working with thousands of machines) to provide uptime guarantees during the roll out process.
--Chris -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
