by harryruhr on 12/25/21, 11:16 PM with 130 comments
by trabant00 on 12/26/21, 7:50 AM
by bushbaba on 12/26/21, 2:41 AM
Hiring your own janitor is cheaper than paying an outsourcing firm.
Building your own office is cheaper than renting one.
Doing your taxes with pen and paper is cheaper than paying turbo tax.
Making your own food is cheaper than eating out. Hiring a cook directly is cheaper than hiring sudexo.
I could keep going. But sometimes it’s not just cost. The biggest two values you get with AWS is 1) reducing time spent outside your business’s core competencies and 2) a vast ecosystem - 3rd party offerings, readily available devs, consulting services, and compliance services.
I’d add that for those having compliance needs. It’s not always as simple as rack and stacking infra. You have to use services that meet the compliance auditors needs.
by sherifnada on 12/26/21, 10:42 AM
Let's say the year is 2012 and Redshift is introduced, completely changing how organizations can generate insights from their data. Running your own datacenter? good luck waiting for the ops team to install something similar! It might take you a couple of quarters assuming they are already competent at it. On the Cloud? Press a few buttons and you're off to the races.
velocity is a competitive advantage
by moltar on 12/26/21, 2:10 AM
But what about comparing the whole ecosystem?
Can you provide a self hosted granular access permission to your RAID? How hard is it to configure and maintain?
Will your colo deflect a DDOS attack?
When you run your own services, you have to reinvent so much it doesn’t seem to be worth it.
by awill on 12/26/21, 4:59 AM
I used to work at a medium sized company, and they saved millions by moving to the cloud, and gained much better availability/performance. It wasn't even close, because that medium-sized company didn't have the expertise to operate the service efficiently. They just bought off the shelf stuff from VMWare etc.. Plus, DR meant paying double.
disclaimer, I now work for AWS.
by savant_penguin on 12/26/21, 3:49 AM
The word competent here is doing a lot of weight lifting.
I know companies in which you have to wait _months_ for a small server to be allocated to your team. AWS does it in seconds
by endisneigh on 12/26/21, 5:10 AM
- use the cloud until you're making so much money that you can afford to hire the sufficient talent to replicate cheaper.
fin
by Clubber on 12/26/21, 1:04 AM
I can see why it's compelling, but for me running my stuff on other people's servers in this day and age is concerning. Like many computing things, it really depends on the situation.
by ThinkBeat on 12/26/21, 9:22 AM
A bad example: If you are with provide X and they change pricing structure and it impacts you 3 times the cost, you can move it without too much hassle.
Once you embrace all the proprietary and fancy features that your cloud provider has, then you are stuck and moving will be a nightmare.
compute/s3 are easy to move. k8s should be easy to move but I have not tried it myself. Database hosting is easy to change as long as you are using an independent product, not a custom database your cloud provider has.
It is much more difficult when you have AWS/Azure pipelines, AWS/Azure Geo location/manipulation AWS/Azure proprietary scaling etc etc
Terraform is supposed to help here but in my experience with TF consultants it is not at all straightforward not compatible with a lot of AWS/Azure offerings.
Then you are stuck and moving will be difficult and expensive. Which of course is the business plan for the cloud providers.
by kyrra on 12/26/21, 1:38 AM
by mark_l_watson on 12/26/21, 1:11 PM
Personally, I miss the days of monolith web applications that were relatively easy to host on a leased server. I continue to be a big fan of Hetzner and their hosted servers as well as their VPSs are very reasonably priced. Another thing that I like about Hetzner, OVH, etc. is that their bandwidth costs are also very reasonable so moving databases and monolith web applications to a similar service does not have to be a big deal.
I think that each company’s needs have to be assessed separately.
by StephenJGL on 12/26/21, 1:41 AM
by BizyDev on 12/26/21, 2:23 PM
But here's is the point that's completely missing from the article. Many choices in organisations are leaded by two wrong drivers :
- Career risk awareness : like we said in the good old days, nobody was fired for buying Sun Microsystems. Same thing applies for Azure and AWS. You're not paying the bill so why looking for a cheaper alternative that might cost you personally a lot. - CV driven decision : on your CV it's better and more valuable to have 3 years of Azure/AWS than having 3 years on OVH/Hetzner/etc.
Finally, as a leader in an organisation, it's always easier to follow the trend rather than trying to convince your coworkers to follow you to a more "exotic" solution.
by agrippanux on 12/26/21, 2:24 PM
by manishsharan on 12/26/21, 4:03 AM
by zerotolerance on 12/26/21, 3:45 AM
by Damogran6 on 12/26/21, 1:37 PM
by throwaway984393 on 12/26/21, 2:21 PM
He's right. Evaluate your needs and use it if it makes sense. Not a very controversial opinion, I think!
The problem is, how do you evaluate your needs if you aren't an expert in either self-hosting or using managed services (AWS)? I think you should treat it like going to a doctor: get two opinions from two different senior professionals in two different specializations. And definitely make an assessment based on real numbers. Try to get ballpark figures from similar-sized businesses about their costs (capex/opex, infrastructure, staff) and requirements (expertise, time-to-market, FRs/NFRs, regulations, etc). Building a business is a huge thing, and how you use technology can either be a hindrance or an accelerator, but it has to fit your use case.
by acd on 12/26/21, 10:08 AM
Datbases and virtual machines tend to be expensive in cloud providers. Steady state workloads.
Object storge tend to be fairly cheap.
There is also cost of vendor lock in if you use propritary cloud technologies such as databases.
You can build open source infrastructure with hybrid solution. Probably less risk of downtime.
by slac on 12/26/21, 2:54 PM
Choosing a large cloud provider is often much greener than doing your own or using a smaller provider.
Carbon is a large cost.
GCP has been carbon neutral for over a decade, AWS and Azure have made big public commitments.
Sourcing clean energy for 1000s of servers is not always easy.
by curious_cat_163 on 12/26/21, 3:58 AM
by nijave on 12/26/21, 3:37 AM
by ksec on 12/26/21, 10:54 AM
If you look at prices from Oracle Cloud ( ignoring whatever feeling you have against it ) than all of a sudden it is extremely attractive.
by mac-chaffee on 12/26/21, 3:33 AM
Could someone elaborate? Is this saying something free like OpenStack would be better than something paid like VMware? Is that really common knowledge?
by sparkling on 12/26/21, 12:46 PM
The "cloud" can just be a blank Debian box on Digitalocean where you have root access _or_ it could be some obscure managed AWS service where all the technical days are abstracted away behind a REST API.
by StreamBright on 12/26/21, 8:25 AM
by MangoCoffee on 12/26/21, 8:08 AM