Hacker News new | past | comments | ask | show | jobs | submit login

Except then you're stuck with a $15K server, and you had to spend all 15K up front. What happens when a component prematurely fails? Better buy two. What about the person-hours you spend with ISPs, CoLo provider, etc? You want network redundancy? Big ISP bills.

Yes, cost per compute measurable (memory, CPU, etc) is higher in the cloud. But what's never mentioned when people complain about the cloud being expensive:

a) ISP and CoLo costs

b) Redundancy/Multiple AZs

c) Backups

d) Failure recovery/cutover

e) Support

f) Monitoring/Health statistics

g) The other goodies that come along with being in the cloud(Lambda, CloudFront, Route53, SQS, etc)

I feel like we're at a point where people should have to justify why they are running their own data centers vs. having to justify why they're running in the cloud. There's obviously many very good reasons to do either, or both, but if you don't already have a data center, you better have some damn good reasons for starting one up.

That $15,000 server is leased across 36 months becoming an OpEx expenditure. On the accounting side this is no different than AWS. So let's say you buy two for failover.

A) Colo is $50-150/U with blended top tier bandwidth, 99th% billing and usually includes remote hands time.

B) Even with 100% redundancy you're still ahead by $3000/month. Please understand Amazon offers absolutely no redundancy built in and nodes go down regularly. It is up to you as a developer to build redundancy around the tools they offer.

C) Amazon doesn't take backups for you. You have to pay for this either way.

D) Again Amazon doesn't handle this for you. You have to pay either way. Buying an exact replica of the hardware I've mentioned and cololocating it elsewhere still puts you ahead by $3000/month.

E) What support do you need? Dell offers same day or even 4 hour parts replacement with the appropriate warranty service. Most Colos offer remote hands for free up to a certain hourly.

F) Lots of ways to handle this. You can use IPMI, built in OS tools, etc. There isn't much exclusive to AWS you can't easily replicate elsewhere.

G) I never said not to use Amazon for anything. In fact you should be building your applications for scaleability INTO the cloud. This is part of the idea behind the whole microservices movement.

  > Except then you're stuck with a $15K server, and you had to spend all 15K up front
I think you missed the part where the parent said "lease it at $400/month (OpEx)"

Cloud doesn't automatically come with that stuff - you need to set up your own failovers, backups and monitoring. Also you still need to administer those servers.

Also, tying yourself exclusively to AWS services is not a good long term strategy because then you have vendor lock-in that's worse than being stuck with some old hardware.

If you don't need the scaling abilities of cloud, then it just doesn't justify the added expense because no matter what you say, you still need people to manage systems.

Yes you do need to know your shit. But that's true for all kinds of products and services any business buys. Someone has to understand the deep weeds Health Insurance at any company (in the USA).

Registration is open for Startup School 2019. Classes start July 22nd.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact