> Should losing a single host machine be a big deal nowadays? Instance failure is a fact of life. Depends on where in your development cycle you are. If you j

> Should losing a single host machine be a big deal nowadays? Instance failure is a fact of life. Depends on where in your development cycle you are. If you just got started and haven't even figured out what you're actually building (prototyping), you shouldn't really use a hosting provider that randomly lose instances. If you're on the other hand have done everything to improve your applications performance, had to resolve through-output issues with a distributed architecture and now running 10+ instances, then losing one host shouldn't impact you too much. But you really shouldn't start this way, it's doing web services the hard way and introduces a lot of complexity you shouldn't want to deal with when you're still trying to find product market fit.