3 ms·
Lack of egress charge is great for write once, read a lot. But for write once, read a handful of times (e.g. a webhook system that basically is write once, rea
by kondro 5y ago
Lack of egress charge is great for write once, read a lot.
But for write once, read a handful of times (e.g. a webhook system that basically is write once, read once of <32KB objects with long history for either redelivery attempts or replaying the entire stream for a point of time), request prices end up being the biggest cost.
- l-lousy 5y agoNot if, as R2 says, they only charge for objects that exceed a single digit request per second threshold. Your write once read once model still only costs as much as the storage at rest would.
- kondro 5y agoI don’t think they mentioned this would be “per object” and I assumed they meant per account. Free per object requests is super game-able. Want 1000 free requests per second, just rotate through 100 identical objects.
- piaste 5y agoBut then you're multiplying your storage costs 100x, aren't you?
- kondro 5y agoWhich are often significantly lower than request (and egress) charges. 1,000 reads per second is 2.6 billion per month. At S3 prices, that wound cost around $1,040. 100x storage is pretty minimal to achieve this. For example: 100x 128KiB = $0.000192/month 100x 10MiB = $0.015/month 100x 1GiB = $1.50/month