4 ms·
I know AWS services put outsized fees on things that don't really have marginal costs (e.g. S3 read operations), because the fees are used to disincentivize non
by derefr 9y ago
I know AWS services put outsized fees on things that don't really have marginal costs (e.g. S3 read operations), because the fees are used to disincentivize non-idiomatic use-cases (e.g. treating S3 as a database by scanning objects-as-keys.)
Under this economic-incentive-system lens, I'm curious whether new AWS services might also be intentionally started out with high premiums, as a sort of economically-self-limited soft launch. Only the customers with the biggest need will be willing to pay to use the service at first, and their need means they're also willing to put up with you while you work out the initial kinks. As you gain more confidence in the service's stability at scale and matching to varied customer demands, you'd then lower the price-point of the service to match your actual evaluation of a market-viable price, to "open the floodgates" to the less-in-need clients.
- nerpderp83 9y agoWell if something needs more burn in time, the last thing you want to do is get thousands or millions of customers. The reliability of a Timex or Toyota has to be high.
- sync 9y agoTangentially related: you can definitely use S3 as a database now, and they seem to encourage it: https://aws.amazon.com/blogs/aws/s3-glacier-select/ https://aws.amazon.com/blogs/aws/s3-glacier-select/
- mrep 9y agoWithout lock support, I wouldn't consider it a database.
- justonepost 9y agoKind of a read mostly database, actually useful for data lake type things.
- IanCal 9y agoYeah I'm really looking forward to this as I often have to get some part of one of many jsonl files that matches some condition. S3 select will likely let me delete a lot of custom code.
- deleted 9y ago[deleted]
- justonepost 9y agoYes, this is standard pricing model for all new tech.