5 ms·
ah, very key. i'd highlight Werner Vogels' recent interview here on lessons learned from setting up S3 itself: https://cacm.acm.org/magazines/2021/3/250706-a-se
by swyx 6y ago
ah, very key. i'd highlight Werner Vogels' recent interview here on lessons learned from setting up S3 itself: https://cacm.acm.org/magazines/2021/3/250706-a-second-conversation-with-werner-vogels/fulltext https://cacm.acm.org/magazines/2021/3/250706-a-second-conver...
"Here is another interesting example with S3. It's probably the only time we changed our pricing strategy. When we launched S3, we were charging only for data transfer and data storage. It turned out that we had quite a few customers who were storing millions and millions of thumbnails of products they were selling on eBay. There was not much storage because these thumbnails were really small, and there wasn't much data transfer either, but there were enormous numbers of requests. It made us learn, for example, when you design interfaces, and definitely those you charge for, you want to charge for what is driving your own cost. One of the costs that we didn't anticipate was the number of requests, and request handling. We added this later to the payment model in S3, but it was clearly something we didn't anticipate. Services that came after S3 have been able to learn the lessons from S3 itself."