amtal · June 12, 2011 22:58
diff --git a/talk.txt b/talk.txt
 Hot Code Reload in the Small: Hot Upgrades in the Large

 Erlang's strongest strength is reliability, and thus uptime. Language design, VM features, and OTP design principles come together to produce code with useful properties. Two important ones are arbitrary error recovery, and hot upgrades. With them, systems with many nines of uptime can be built.

 This talk will focus on hot upgrades. We will start in the small, with low level mechanisms. Then, using examples and demonstrations, we'll cover the conventions and libraries that bring hot upgrades to the large.

 By the end, you'll see how a system can be kept running non-stop despite being patched, updated, extended, and partially rewritten!
	Hot Code Reload in the Small: Hot Upgrades in the Large

	Erlang's strongest strength is reliability, and thus uptime. Language design, VM features, and OTP design principles come together to produce code with useful properties. Two important ones are arbitrary error recovery, and hot upgrades. With them, systems with many nines of uptime can be built.

	This talk will focus on hot upgrades. We will start in the small, with low level mechanisms. Then, using examples and demonstrations, we'll cover the conventions and libraries that bring hot upgrades to the large.

	By the end, you'll see how a system can be kept running non-stop despite being patched, updated, extended, and partially rewritten!