News for hackers. Stuff that matters.
Re:Ways to reduce the costs of an HTTP(S) API on AWS by markonen on Friday December 13, 2019 @12:47PM (#21783667)
My read was that they actually saved over $8000 per month:

- They mention that the initial savings of $1500/mo from omitting unnecessary headers was 12% of their egress cost (so the total before this was $12500)

- Then they got an additional 8% of savings by increasing the ALB idle connection timeout to 10 minutes (down to $10120)

- Finally they said they saved $200 per day by switching to a lighter TLS certificate chain ($6000/mo, so down to $4120)

None of those steps seem to have required any meaningful amount of development work. Let's say this took a developer one week? The return on that effort would be $100k a year, or $2500/hour for the first year alone.

Re:Ways to reduce the costs of an HTTP(S) API on AWS by blazespin on Saturday December 14, 2019 @06:11AM (#21788900)
Considering they have enumerated this for others to pick up and execute quickly, they may have just saved the wider industry potentially 100s of thousands per month.

Give and take is an open source attitude. It doesn’t always have to be about source code, sometimes it can be about cost savings techniques such as this.

Re:Ways to reduce the costs of an HTTP(S) API on AWS by Bombthecat on Saturday December 14, 2019 @02:56AM (#21788376)
Maybe it is a good thing that cloud is so expensive here.. The internet traffic is bloated enough already :)