4 ms·
Every programmer? In our team, only like two, maybe three programmers are concerned about our AWS architecture at all. I don't really know why everyone in the
by Hamuko 7y ago
Every programmer?
In our team, only like two, maybe three programmers are concerned about our AWS architecture at all. I don't really know why everyone in the team should know how much the individual components of AWS cost. They should just know how to not write performance-destroying code that mandates scaling instances up.
- growtofill 7y agoThe title is a mock of “Latency Numbers Every Programmer Should Know”[0], although these are (a) limited to a popular, yet not exclusive platform, (b) subjective to change at any moment. [0]: https://people.eecs.berkeley.edu/~rcs/research/interactive_latency.html https://people.eecs.berkeley.edu/~rcs/research/interactive_l...
- bpicolo 7y agoEagerly await the follow up: Falsehoods programmers believe about AWS costs
- jraph 7y agoAnd then: - 10 reasons why AWS costs so much. #7 is mind-boggling. - AWS costs considered harmful
- chrisseaton 7y agoIt's a pattern title. It's not meant to be taken literally and most reasonable people wouldn't read it that way.
- mjlee 7y agoI don't think that every programmer should know it off by heart. I do think it should be a reasonably common skill to make common tradeoffs without too much investigation. Besides, the title is an homage to the Latency Numbers article which follows a similar concept. You don't need to memorise numbers, but you probably should be able to reason about them in very vague terms.
- katzgrau 7y agoIt's not just code, and it's not always obvious. AWS' tools (as robust as they seem at first) may not give you the low-level insight that you need to understand where you can really cut down on expenses. I just reduced my AWS bill from about $5.5k/mo to $3k/mo. The rise in price was only slightly outpacing the app growth for a while, and it was very gradual. When the forecasted bill was $6k it became a major priority.