No reviews yetBe the first to leave a review for Files SDK
Useful abstraction, but the real test is where it leaks: provider-specific errors, multipart uploads, and list semantics. If those stay predictable across S3, R2, GCS, and Azure, the swap cost is much lower.
Report
This is exactly the kind of abstraction layer I've been waiting for. I've personally wasted hours setting up different adapters for S3 vs Blob storage across projects having one consistent API with web-standard I/O means I can finally stop copy-pasting storage boilerplate. The native client escape hatch is a smart touch too, shows the team thought about real-world edge cases. Congrats on the launch!
Report
Another router, how is this different from the others?
Report
How is it any different from hundreds of others ?
Report
“Unified storage” is one of those phrases that sounds boring until you’ve actually fought with S3, GCS, and blob storage in the same week. Then it sounds like salvation.
Nice! agree with the comments. You don't know how important it actually is until you have to fight with real storage. Glad to see you helping on this. All the best!
Useful abstraction, but the real test is where it leaks: provider-specific errors, multipart uploads, and list semantics. If those stay predictable across S3, R2, GCS, and Azure, the swap cost is much lower.
This is exactly the kind of abstraction layer I've been waiting for. I've personally wasted hours setting up different adapters for S3 vs Blob storage across projects having one consistent API with web-standard I/O means I can finally stop copy-pasting storage boilerplate. The native client escape hatch is a smart touch too, shows the team thought about real-world edge cases. Congrats on the launch!
Another router, how is this different from the others?
Build Check
Nice! agree with the comments. You don't know how important it actually is until you have to fight with real storage. Glad to see you helping on this. All the best!