4 ms·
I don't think it's safe to assume that paying for that service being done by someone maintaining 1000+ machines is necessarily going to be more expensive than p
by tomkarlo 16y ago
I don't think it's safe to assume that paying for that service being done by someone maintaining 1000+ machines is necessarily going to be more expensive than paying to do it in-house for 10 or 100. It's generally going to be significantly more cost-efficient on a per-machine basis to have someone administrating 1000 machines vs. 100. If nothing else, the cost of specifying and purchasing hardware and getting staff up to speed on it is going to be spread much more efficiently, as is the cost of 24x7 oversight and backup hardware. Not to mention they're probably buying all that hardware significantly cheaper.
- squanderingtime 16y agoI think we are agreeing here, we're just phrasing it differently. I didn't mean to imply there was a direct cost comparison; just that part of your payment is for them to fund someone's paycheck. In the grand scheme of things it's definitely cheaper to maintain a high ratio of machines-under-maintenance to systems administrators. That being said, the difference is Amazon pays an administrator to watch potentially thousands of machines of which you may be using a tiny fraction. You're essentially paying for a very tiny fraction of an admin's time (somewhere) who isn't vested in your business nor does he care that your site is acting wonky. He's just answering and working through tickets (if you bought support). Cloud providers can be come markedly less helpful the instant you (attempt to) deviate from the very carefully maintained cookie-cutter pattern they've set out for you.
- tomkarlo 16y agoWorking at a company with hundreds of machines and dedicated admins for them, I can tell you that unless the problem has immediate revenue impact, they're not going to handle it a whole lot differently from a cloud provider - you have to cut a ticket, it's prioritized, and it goes in the queue.