Paul G. Allen wrote:
Personally, I don't like the idea of farming anything out, especially if
we (meaning the company that needs the new service) have the skills
internally to develop and maintain it. Some of the reasons I feel this
way are because it makes us beholden to the company we've farmed it out
too, we have to continue to pay them, we are limited in upgrade options,
changes, enhancements, etc., and we are trusting someone else with our
data.
Two comments:
First, have you looked at their *prices*. AWS is an unbelievably good
deal on bandwidth. I can't get any ISP to match their price until the
250Megabit commitment level.
Second, startups have little choice. AWS requires no precommitment.
You don't pay until after you use it, and you don't have to precommit to
a 10Megabit line until you are actually using 10 Megabits.
Basically, as a startup, I'd start by using AWS with the intent of
pulling it back in-house if things actually took off. Besides, having a
ready-made Amazon image that I can just recall and run immediately
solves any disaster planning needs.
If the ISP's don't answer, they are going to lose almost all their
low-end colo people to Amazon.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
