Earlier quoted context omitted.
Business continuity: Providing a good SLA isn't in the AWS business model, which allows for widespread, lengthy outages. They have a so-so SLA and if they miss you get AWS credits, big whoop. They make their money on people who are insensitive to high cost, middling performance and reliability. Not sure about the other providers. At a certain point it's cheaper and easier to do it yourself than to support a hybrid cl…
Sure, but is there some structural reason AWS can’t have an offering tailored to requirements like yours, or have they simply not bothered to start one yet?
Ask HN: Why aren't you using a public cloud?
41–50 of 73 posts
Re: Ask HN: Why aren't you using a public cloud?
#42Dedicated 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…
Even if you're running everything else serverless and have no compute time at all? I know a VOD training service runs serverless with videos on S3 and they're very successful.
You can be successful on AWS, but you're leaving money on the table, and for relatively commodity services it's just a question of time before a competitor realise they can do the same with much better margins and lower prices elsewhere.
If your hosting is a small portion of your costs, that might not matter, so I have certainly run services on AWS too, and do in my current job as well, but it's a very expensive convenience. I've yet to come across any systems I know the internals off that couldn't cut hosting costs by moving off public cloud services.
Re: Ask HN: Why aren't you using a public cloud?
#43Most of my success comes not from selling to IT but the CFO or Board. Once they realize they can eliminate a dozen or so SAN Storage or networking engineers then the cloud doesn’t seem so expensive after all.
Re: Ask HN: Why aren't you using a public cloud?
#44Dedicated 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…
Re: Ask HN: Why aren't you using a public cloud?
#45Cloud migration specialist here. Biggest thing I see is the culture. Large shops will be 80% infrastructure and 20% developers. Infrastructure folks almost always will be fired after a successful cloud migration. Middle Managers want to keep a large staff and budget to justify themselves. CIOs often come up through the infrastructure career path and don’t trust firewalls if they aren’t made by Cisco or SANs that they…
Edit: There is no silver bullet. Model your needs, make sure your model is accurate. You might still be wrong if your model doesn’t match reality due to unanticipated deviations.
Re: Ask HN: Why aren't you using a public cloud?
#46Re: Ask HN: Why aren't you using a public cloud?
#47Do you Uber to work everyday? I don't. I use it occasionally but most of the time I drive my car to work. Cloud is best for handling spike workloads, not day to day.
You can afford to let the servers handling your base load get much closer to capacity when you know you can scale up near instantly instead of having to provision new servers.
This is the biggest reason for me to run services that are prepared to run on public clouds, though it's very rare I've ever needed to make use of it - the kind of spikes that are severe enough and long lasting enough to be worth provisioning cloud instances for tends to be very rare for most people.
Re: Ask HN: Why aren't you using a public cloud?
#48Earlier quoted context omitted.
Even if you're running everything else serverless and have no compute time at all? I know a VOD training service runs serverless with videos on S3 and they're very successful.
I don't have the numbers here, but I'm pretty sure the same idea applies for serverless. If you have a predictable load, you can always find a much cheaper alternative once you pass a certain threshold. The cloud is never about cost, it's about flexibility.
It's not an order of magnitude, but it's something. Probably not worth the effort, for most, though, and I have no idea if "dedicated box" services can approximate something similar.
Re: Ask HN: Why aren't you using a public cloud?
#49Regulatory compliance, risk management, security controls, business continuity/SLAs, and cost. Financial services industry.
Those seem like problems the public cloud providers would be highly motivated to solve. Why haven’t they?
Re: Ask HN: Why aren't you using a public cloud?
#50I suspect there's still a lot of FUD regarding public cloud as well as on-prem admins and engineers actively pushing back for fear of losing their jobs. (I've seen this in action) There certainly are legitimate reasons not to move to public cloud, but it shouldn't be an emotional one. Measure cost (including manpower), SLA's, performance, governance, and compliance. After that it should be simple to stay on-prem, go…
In terms of actual hosting costs, I've more than once been prepared to offer clients to move them off AWS and guarantee my fee will simply be a percentage of the savings - I've seen clients cut hosting cost between 50% and 90% on moving from AWS to dedicated hosting, and cut their devops costs at the same time.
For someone doing admin/devops who wants to maximize billable hours, recommending AWS would be better than recommending on-prem - it's all remote, no annoying travel etc., and you're likely to make more money, and at the same time you ironically gets less pressure from managers who have been told cloud will cut their costs.
> Doing a lift and shift can be cost-effective, but decomposing these applications and rebuilding them in serverless would probably provide significant savings.
Even if you rebuild them as "serverless" you'd probably end up saving far more by deploying said "serverless" apps on dedicated hosting providers for the base load.