AWS costs every programmer should know (2019)
david-codes.hatanian.com
AWS costs every programmer should know (2019)
1–10 of 163 posts
Re: AWS costs every programmer should know (2019)
#2Re: AWS costs every programmer should know (2019)
#3The one AWS service that I pay for is S3 Glacier Deep Archive.
It is very cheap insurance for knowing with virtual certainty that your data exists. Egress is expensive ($100/TB last I checked), but in the target use - backups of last resort - I will be very glad to pay that to have my data back. And if all goes right I'll never pay it.
Personally I find ordinary S3 far too expensive to justify. Not so with Deep Archive.
Note, I work for AWS. Opinions are my own.
Re: AWS costs every programmer should know (2019)
#4It's interesting how AWS can keep so high prices on these. But it's just the beginning, the real money comes from when they convince you to run over a dozen vms/containers (all needing storage etc of course).
You need to be triply redundant on 3 availability zones, (3x) both with the RDS db cluster and app containers (2x) . And then have separate dev/staging/prod envs (3x). That's 18x.
You can then get a pat on the head ("pass AWS well-architected review"). Then they innovate "serverless" stuff where you can pour developer man months and years to save on this overpriced things by making everything more complex, hard to monitor/debug and learn new aws specific techs, so you can get faux savings. Here they're buying your long term lock-in by getting AWS specialists and advocates on your long term payroll. They're doing certifications and investing in AWS careers that can carry over to the next employer too.
And don't even get me started on how much work by this time has gone to build the infra-as-code to manage the rube golderg machine, you'll (seriously) have more lines of CDK code than app logic (that was slower to develop & harder to debug than your actual app code per line).
Just about now someone in your newly grown cloud herding engineering org champios the idea "I know what will help, let's start using Kubernetes". They've probably never costed / self administered a server in production use, or if they have, they know to keep quiet.
Re: AWS costs every programmer should know (2019)
#5The one AWS service that I pay for is S3 Glacier Deep Archive. It is very cheap insurance for knowing with virtual certainty that your data exists. Egress is expensive ($100/TB last I checked), but in the target use - backups of last resort - I will be very glad to pay that to have my data back. And if all goes right I'll never pay it. Personally I find ordinary S3 far too expensive to justify. Not so with Deep Archi…
It might be cheap now but there is absolutely no guarantee that one day they'll send out a fairly nondescriptive AGB update email and increase the prices without you knowing. Then because all these ever so helpful cloud services don't allow you to create payment caps the costs can explode any day. It's all one executive decision away.
Re: AWS costs every programmer should know (2019)
#6The one AWS service that I pay for is S3 Glacier Deep Archive. It is very cheap insurance for knowing with virtual certainty that your data exists. Egress is expensive ($100/TB last I checked), but in the target use - backups of last resort - I will be very glad to pay that to have my data back. And if all goes right I'll never pay it. Personally I find ordinary S3 far too expensive to justify. Not so with Deep Archi…
It might be cheap now but there is absolutely no guarantee that one day they'll send out a fairly nondescriptive AGB update email and increase the prices without you knowing. Then because all these ever so helpful cloud services don't allow you to create payment caps the costs can explode any day. It's all one executive decision away.
I feel like AWS has a pretty good track record at this point for not increasing prices - certainly to the point that I trust them not to pull an Oracle. (Hypothetically, my volume of data stored with them is low enough that even a 10x gouge would just make me angry, not wound me financially. There's not a mechanism for these archives to incur explosive costs, but your point is why I avoid other less-predictable cloud services.)
Re: AWS costs every programmer should know (2019)
#7The one AWS service that I pay for is S3 Glacier Deep Archive. It is very cheap insurance for knowing with virtual certainty that your data exists. Egress is expensive ($100/TB last I checked), but in the target use - backups of last resort - I will be very glad to pay that to have my data back. And if all goes right I'll never pay it. Personally I find ordinary S3 far too expensive to justify. Not so with Deep Archi…
It might be cheap now but there is absolutely no guarantee that one day they'll send out a fairly nondescriptive AGB update email and increase the prices without you knowing. Then because all these ever so helpful cloud services don't allow you to create payment caps the costs can explode any day. It's all one executive decision away.
Historically speaking, in the ~15 years AWS has been around, have they ever increased prices for any service? In my experience, they've only ever decreased prices of their services as advances in tech have been made rather than increasing them. Sure some start out being expensive cough Macie and Fargate cough but they didn't increase prices after being launched as far as I'm aware.
Assuming they never have increased a price in 15 years, that doesn't prevent them from doing so, but it's a confidence inspiring track record.
I have about as much confidence that AWS won't raise prices on existing services/features as I do that Google will eventually kill another good project - https://killedbygoogle.com/
Re: AWS costs every programmer should know (2019)
#8https://colin-scott.github.io/personal_website/research/inte...
Great little article thank you, one thing, can you add the unit cost per mont details for storage and bandwidth, it makes a difference in calculating the cost, not the same to asume $0.10 TiB/Month or $0.10 GiB/Month, I think that data would be most useful without having to go AWS for verification.
Re: AWS costs every programmer should know (2019)
#9Earlier quoted context omitted.
It might be cheap now but there is absolutely no guarantee that one day they'll send out a fairly nondescriptive AGB update email and increase the prices without you knowing. Then because all these ever so helpful cloud services don't allow you to create payment caps the costs can explode any day. It's all one executive decision away.
I feel like AWS has a pretty good track record at this point for not increasing prices - certainly to the point that I trust them not to pull an Oracle. (Hypothetically, my volume of data stored with them is low enough that even a 10x gouge would just make me angry, not wound me financially. There's not a mechanism for these archives to incur explosive costs, but your point is why I avoid other less-predictable cloud…
Don’t be silly. It’s a game theoretic certainty that they will indeed pull an Oracle.
Re: AWS costs every programmer should know (2019)
#10It's interesting how AWS can keep so high prices on these. But it's just the beginning, the real money comes from when they convince you to run over a dozen vms/containers (all needing storage etc of course). You need to be triply redundant on 3 availability zones, (3x) both with the RDS db cluster and app containers (2x) . And then have separate dev/staging/prod envs (3x). That's 18x. You can then get a pat on the h…
> You need to be triply redundant on 3 availability zones, (3x) both with the RDS db cluster and app containers (2x) . And then have separate dev/staging/prod envs (3x). That's 18x.
Why would you care about the redundancy on staging / dev?
Just making up things to inflate AWS costs now.