I always had in mind that certain information would be backed up in
some way. This would allow lifeguard to restarted if it fails and pick
up where it left off. The instance list is really the only thing that
needs to be saved. This could be flushed to a file at strategic times
(like a write through cache). Another option is to use SimpleDB. I
don't want to just implement this with SimpleDB because that service
is still restricted. Probably the best option is to implement an
instance list backing store, via an interface. We'd still use the
in-memory list for fast response, but there would be a module to call
to flush dirty values out. I could provide a disk based version and a
SimpleDB version. I imagine a MySQL version would be nice to have.
Taking this to the next level would be a hot backup lifeguard pool
manager (running on another server). This would be a lot easier to
implement if the instance list backing store were in SimpleDB or a
host MySQL server (i.e. outside of the lifeguard pool manager instance
itself).
David