Live data from Hacker News

Ask HN: Why aren't you using a public cloud?

news.ycombinator.com

1–10 of 73 posts

Re: Ask HN: Why aren't you using a public cloud?

#2
Old culture and security concerns being in finance. Though that's breaking down. Once you adopt a product built on the cloud (SaaS offering), the first level of integration is nightmare from the corporate datacenter. Once it takes the toll, thats when you begin to see the mindset change.

It's been 2 years of grind and umpteen number of powerpoint but I see a sea change and hopefully soon....

Re: Ask HN: Why aren't you using a public cloud?

#7
Dedicated hosting is much better bang for your buck, especially for bandwidth. If you do something like video streaming and have relatively predictable loads, I've found that you have to pay at least an order of magnitude more with public cloud compared to dedicated servers on OVH or Datapacket. Maxing out a 2gbps server on Datapacket would cost you just $320/month for 648 TB of outgoing bandwidth monthly, versus at least $6,480 just for the bandwidth on Amazon S3.

For venture-backed startups with an emphasis on growth or large scale enterprises, the convenience of the cloud may outweigh the cost premium. But for small to medium size organizations where server load doesn't fluctuate on a day-to-day basis, I haven't yet been convinced that the cloud offers a good enough value proposition.

Re: Ask HN: Why aren't you using a public cloud?

#8
Dedicated servers are now as easy to manage as cloud vms because good dashboards + management tooling have become cloud agnostic. I use Kubernetes + Rancher to manage a cluster of dedicated servers and it's a fraction of the cost as a public cloud.

Re: Ask HN: Why aren't you using a public cloud?

#9
I’ve worked in a few different settings on large-scale scientific computing. For those applications:

- Not cost-efficient at large scale. When you expect and plan to run thousands of nodes at near 100% CPU and memory usage for years at a time, running a machine room can still be less expensive.

- Specialized hardware not available in public clouds, e.g., very low latency networks configured in an optimal topology.

- Lack of control over hardware upgrade schedule. E.g., a cloud probably won’t give you those shiny new GPUs as early as you can shove them in your own servers.

The balance is shifting in many of these areas, and there’s plenty of scientific computing that can use a public cloud now. But I still wouldn’t use it for problems that are both highly CPU-intensive and require low latency networks, especially if I have long-term workloads.

Post reply on HN