I can't really get into specifics, but the particular issue that we have with DO (and it really is specific to DO/droplets) makes it a complete no-go for our new product architecture.
It doesn't save us money if we can't use it.
As for my reasons being weak, you might have read other places in this thread where I've mentioned that I'm responsible for
a) a multi-million dollar infrastructure,
b) across clouds and on-prem in tier 1 datacenters
c) have been in this field for a long time.
Odds are that I'm not a total idiot, that I have good information and that I know what I'm doing here.
You are probably an expert in your area but the original poster was talking about much smaller shops. That's the point being missed for every multi-million dollar spender there are thousands of smaller projects paying 10x the cost because they think they will be you one day and it is cheaper to build on that stack from day one.
Yeah, I'm saying that you can use this cost effectively at smaller places too.
When I think of my core Terraform infrastructure that I can spin up for any project, the only resource with a recurring AWS/Google/Azure cost is NAT Gateways. You can get very cost-competitive with the instances themselves with reservations and/or spot, depending on your architecture. The costs of the big clouds and the small ones is basically the same here.
The way the cost balloons out of control for most companies is for things like S3 access (applications that HEAD the bucket every 60 seconds and hit the API request cash register), or managed services like EKS, Amazon ElasticSearch, etc. It's in the "oh I don't have to learn how to manage X application" where cloud gets expensive.
Smaller providers solve that problem by not even giving you that option. It's not that AWS is expensive, it's that they give you rope to hang yourself with.
Except that in smaller places time is of the essence I we don't have enough to learn the full extent of AWS and I'll save my time and money by using a droplet.
Learning AWS does have a cost. Money I'd rather spend on learning and mastering standard, open and portable systems.
That's not a triviality - C++ has the same problem, if you have a single ezpert individual it's great, but if you have a team, and some are very green, it will be a nightmare.
Small startups use junior talent for most services. They are not hiring the best hr team, marketing, sales and development. They don't have unless amount of money. They will pick one or two areas where they have an advantage and hire a strong person or two.
I think we have wildly different expectations of the scale of "small startups".
If you can afford to full-time hire an entire hr team, an entire marketing team, an entire sales team and an entire engineering org, then you're able to pay an AWS bill.
It doesn't save us money if we can't use it.
As for my reasons being weak, you might have read other places in this thread where I've mentioned that I'm responsible for
a) a multi-million dollar infrastructure, b) across clouds and on-prem in tier 1 datacenters c) have been in this field for a long time.
Odds are that I'm not a total idiot, that I have good information and that I know what I'm doing here.