On 5/31/07, Tracy R Reed <[EMAIL PROTECTED]> wrote:
Bob La Quey wrote:
> Nice work. I am left wondering though what the
> advantages/diadvantages are over using say
> Amazon EC2.
It is nice to have full control over the hardware and not having to
worry about the ephemerality of your data when inside an EC2 instance.
If our EC2 instance went down some kplug member would have to set it up
again and restore the data from backup etc.
It is also nice to have someone else take care of all that.
I suspect that their failure rates are at least as good as
kplugs any way.
BTW I don't see why it would be that hard to automate
the restoration of an EC2 based service. Just store the
appropriate image in S3 then poll the EC2 instance. If
it goes down launch another.
I suppose all of Amazon could go down but then
Sparkplug could too.
EC2's real strength is in quickly rolling out new clusters of machine
for fast response cpu power. I am using it to host my website only
because I like their cheap bandwidth and I am willing to risk having to
restore all of my data from backup.
Agree about the response to loads. Maybe we should try to
induce a slashdot test.
BobLQ
PS. I am _not_ faulting Josh or anyone in KPLUG for
building/running Sparkplug, after all this is essentially
a hobby and if folks like doing that more power to em.
I am just quite intersted in the tradeoffs.
I am building a boat of my own design. Nothing could
be less pragmatic than that. (Well maybe designing
and building an airplane; those guys really are nuts :)
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
