There are a lot of hidden costs to the inflexibility of running local hardware. With hosted you get: - 24h availability of mixed skills sets (e.g. Cisco at 4am) - ability to expand if under load/attack - costs in proportion to revenue (sales go down you can have lower opex next month) - ability to move resource around the globe in days Some of this becomes critical if you get to point that SLAs matter.
Why Some Startups Say the Cloud Is a Waste of Money
51–58 of 58 posts
Re: Why Some Startups Say the Cloud Is a Waste of Money
#52http://www.wired.com/wiredenterprise/wp-content/uploads/2013... I guess "casual dress code" at startups these days means exposed feet on the table, right where your co-workers can see (and perhaps smell) them. And why does he have a roll of toilet paper under his monitor?
> And why does he have a roll of toilet paper under his monitor? For use as facial tissues.
Having a roll of toilet paper on your desk is incredibly tacky.
Re: Why Some Startups Say the Cloud Is a Waste of Money
#53Earlier quoted context omitted.
> And why does he have a roll of toilet paper under his monitor? For use as facial tissues.
At the risk of sounding facetious, there's an app for that: facial tissues. Having a roll of toilet paper on your desk is incredibly tacky.
Re: Why Some Startups Say the Cloud Is a Waste of Money
#54The right tool for the right workload... If you only need five servers on the net, VPS' make sense (cheap, easy to spin new ones, etc...). If you need 10, physicals (aka dedicated), might make sense. They're cheaper per Ghz, but take longer and need more skills to bring online. Nees more? Colo might make sense. Also, as you expand to physicals and colo, using some of the other options for specific needs might make se…
For the business person:
- Heroku first (if your dev hasn't setup a VPS, dedicated server before)
- Once something like Heroku starts costing you more than $500 a month, it's time to pay to move it to a VPS like Linode or digital ocean (new than Linode but cheaper). You can start out with just a server for the app and one for the DB
Re: Why Some Startups Say the Cloud Is a Waste of Money
#55Earlier quoted context omitted.
well, it's actually a very easy thing to quantify, but the cost/benefit analysis is different for every kind of company and computing requirement - the REAL problem is it takes experience in running your own datacenter or at least colocated hardware to perform this analysis, and almost nobody does this because they all work for large internal IT orgs or the cloud providers themselves.
You'd be surprized how fast that experience is gained. Try putting a server in colo and you'll be surprised. There is nothing to it. NOTHING. Don't buy the hype. Try it and see for yourself.
a half cabinet + sufficient power and smart power distribution + real networking + remote hardware level access + backup is where it starts to get complicated, but profitable.
Re: Why Some Startups Say the Cloud Is a Waste of Money
#56That is why i have been asking why all these Cloud Providers dont offer dedicated machines.
Re: Why Some Startups Say the Cloud Is a Waste of Money
#57>> 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…
There'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.
Re: Why Some Startups Say the Cloud Is a Waste of Money
#58There are a lot of hidden costs to the inflexibility of running local hardware. With hosted you get: - 24h availability of mixed skills sets (e.g. Cisco at 4am) - ability to expand if under load/attack - costs in proportion to revenue (sales go down you can have lower opex next month) - ability to move resource around the globe in days Some of this becomes critical if you get to point that SLAs matter.
If you want to maintain that flexibility, you can't use reserved and therefore your costs rise proportionally.