| ▲ | mtndew4brkfst 3 hours ago | |
I can't see how Amazon is incentivized to avoid making any changes that break compatibility for their imitators, so long as their first party SDKs continue working. Standardized feels like it should be suffixed with "as long as Amazon doesn't ever feel like evolving the product further". | ||
| ▲ | necubi 2 hours ago | parent | next [-] | |
It would be pretty shocking for Amazon to break the S3 API at this point. There is a huge 3rd party ecosystem that would be affected. For example, in Rust land the object_store crate is at least as popular as the official SDK. | ||
| ▲ | uroni 3 hours ago | parent | prev | next [-] | |
There is a lot of software that directly implements the HTTP S3 API. That API is also documented by Amazon. E.g. the last implementation I saw was by DuckDB https://github.com/duckdb/duckdb-httpfs/blob/main/src/s3fs.c... | ||
| ▲ | bigbuppo 3 hours ago | parent | prev [-] | |
If amazon changes the API they've angered their entire customer base that relies on the API. Sure, some will stick around if they're fully entrenched by the ecosystem, but others will be able to leave, and they will, because hey, S3 is a standard-ish API. | ||