S3 was/is optimised for a specific bunch of use cases.
Because EC2's hypervisor was (when it was launched) lacking features (no hot swap, not shared block storage, no host movements, no online backup/clone, no live recovery, no Highly available host failover ) S3 had to step in to pick up some of the slack that proper block or file storage would have taken.
For better or for worse, people adopted the ephemeral style of computing, and used s3 as the state store.
S3 got away with it because it was the only practical object store in town.
The biggest drawback that is still has (and will likely always have) is that you can't write parts to a file. its either replace or nothing.
But that's by design.
So I suspect it'll stay like that.
Because EC2's hypervisor was (when it was launched) lacking features (no hot swap, not shared block storage, no host movements, no online backup/clone, no live recovery, no Highly available host failover ) S3 had to step in to pick up some of the slack that proper block or file storage would have taken.
For better or for worse, people adopted the ephemeral style of computing, and used s3 as the state store.
S3 got away with it because it was the only practical object store in town.
The biggest drawback that is still has (and will likely always have) is that you can't write parts to a file. its either replace or nothing.
But that's by design.
So I suspect it'll stay like that.