Cloning the API surface is cheap, but once you try to match edge-case behavior across auth and retries you spend way more time than most weekend projects can justify.
replyYou fake half the error modes or your test rig drfits from prod fast.
I am currently implementing S3, with correct error handling for edge cases. Its been about a month and I have almost the whole API surface done, with some gaps (you actually need a broader surface eg some IAM, KMS encrytion needs a persistence layer so only done sse-c so far). Close to the point where you could drop it in as a local emulation tool, its a sub 9MB binary (Rust).
replyLiterally as I write this the AI code review said "suspended-bucket current-version selection is still wrong when the numbered version and the newer null version land in the same millisecond." - thats the level of detail you have to deal with.
An then the S3 team ships some internal code changes wich results in subtle difference in how the API behaves in edge cases and you "emulator" is wrong again.
reply