4 ms·
Sounds good, but not true: https://www.awsgeek.com/AWS-History/ https://www.awsgeek.com/AWS-History/ S3 launched in 2006. EC2 didn't go GA until 2008. Elasti
by amzn-throw 2y ago
Sounds good, but not true: https://www.awsgeek.com/AWS-History/ https://www.awsgeek.com/AWS-History/
S3 launched in 2006.
EC2 didn't go GA until 2008.
Elastic Block Store (a proper block store) showed up in 2008 too, actually went GA before even EC2.
S3 was for the longest time pitched as storage for the internet, and remains so today.
I super doubt these limitations are there because of any EC2 requirements.
- easton 2y agoI think OP isn’t saying S3 was created to service EC2, but people deploying EC2 used it as a substitute for EC2 having certain features.
- KaiserPro 2y ago> I super doubt these limitations are there because of any EC2 requirements. I think you are misreading me, but to be fair, I was being vague about timelines. my main thrust is that S3 is dominant because EC2 was/is lacking. S3 is optimised for uptime and consistency, which means that its brilliant at mostly static file hosting. It will work for more dynamic state type stuff, its just not really designed for it (see https://xeiaso.net/blog/anything-message-queue/ https://xeiaso.net/blog/anything-message-queue/) making your own object store that is fast, durable and available and has another feature is really really hard to do at scale. Its far easier to put up with s3 than make your own.