4 ms·
Historically, they've been scared of versioning their APIs (not many services have done it, dynamodb has, for example). It leads to a "bad customer experience"
by Twirrim 2y ago
Historically, they've been scared of versioning their APIs (not many services have done it, dynamodb has, for example).
It leads to a "bad customer experience", having to update lots of code, and also increases maintenance costs while you keep two separate code paths functional.
There's a lot about the S3 API that would be changed, including the response codes etc., if S3 engineers had freedom to change it! I remember many conversations on the topic when I worked alongside them in AWS.
- andrewxdiamond 2y agoIt’s quite insane the levels of effort S3 engineers put in to maintain perfect API compatibility. Even tiny details such as whitespace or ordering have messed up project timelines and blocked important launches.
- Twirrim 2y agoAll meeting some random arbitrary, maybe not even conscious, decision made by an early S3 engineer when they were implementing something.