4 ms·
>> That’s $324,000 a year. But for just $120,000, the company could buy all the physical servers it needed for the job What about power, cooling, rent in the b
by bluedino 13y ago
>> That’s $324,000 a year. But for just $120,000, the company could buy all the physical servers it needed for the job
What about power, cooling, rent in the building for the room you're keeping them in, backup generator, internet connectivity, administration costs (setup, repairs, installation), etc?
>> “The public cloud is phenomenal if you really need its elasticity,” Frenkiel says. “But if you don’t — if you do a consistent amount of workload — it’s far, far better to go in-house.”
Yup.
- csears 13y agoThere's also the an opportunity cost to consider if your actual demand turns out to be higher than projected and you're not able to scale up to meet it. I think we'll see more companies using a hybrid model where you can run your steady-state workload level on dedicated gear but with the ability burst into a cloud to handle peaks and flash demand.
- Gravityloss 13y agoYou can have considerable reserve capability and it's still cheaper than the cloud. Also renting dedicated servers can be really fast.
- nasalgoat 13y agoMy experience with cloud overflow configurations is that it never works as nicely as you expect, due to a lot of the drawbacks of cloud infrastructure such as variable performance and latency issues.
- mjolk 13y ago>What about power, cooling, rent in the building for the room >you're keeping them in, backup generator, internet >connectivity, Most companies that I've dealt with just rent space in a colo and those costs, plus bandwidth, are far less than $200k. >administration costs (setup, repairs, >installation), etc? It doesn't take that long to rack and stack. Maybe a day for 20 servers if you're doing it alone.
- snowwolf 13y agoAnd how many extra 'DevOps' people has the company now had to employ to manage these physical servers, and what is their annual salary? This never seems to be factored into the calculations.
- beat 13y agoThat was my first thought, too. Physical hardware == more staff. Also consider the risk management of keeping your security up to date, and the opportunity costs of making it easy to use for developers. Spend some time in old-school enterprise, and you'll see just how much pain and grief can happen. Remember, Amazon built its cloud not for the public, but for itself! The cloud gave them a clean separation of duties and cost management between application development and operations. That sort of thing can save large amounts of money and bureaucratic headache. They started selling AWS to the public only after they had a stable system that could produce excess capacity, which could then be resold.
- purple_horse 13y agoWith modern tools like Fully Automatic Install and Ansible/Puppet it shouldn't be any more than for a Cloud service.
- beat 13y agoBut once you have a legacy system, getting the modern tools in there can be a real pain. Instant snowflake, just add expensive and archaic enterprise middleware.
- purple_horse 13y agoTrue, but the article is talking about a startup building from scratch.
- simonebrunozzi 13y agoThe "excess capacity" is a pure myth. When AWS started, it was using a set of Data Centers which had nothing to do with Amazon.com (the Retail part of it). Now Amazon.com is just another (big) customer of AWS. Disclaimer: I work for AWS.
- hhw 13y ago$120,000 worth of servers is maybe 2-3 cabinets. $1100/mo /w 40A @120V each in most major markets, so let's just say $3,300/mo. Add in a 1Gb commit on a 10Gb link of quality bandwidth for another $2,000/mo, and all-in-all you're looking at $5,300/mo or $63,600/yr in operating expenses. Considering the hardware will probably last you 3 years, the hardware cost is actually only $40,000/yr, for a total of $103,600 vs $324,000. You'd easily be cutting your costs by 2/3rds.