Suggestion: Consider integrating OpenDAL for unified object storage support · Issue #76 · gigapi/gigapi · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you for your excellent work on gigapi. It's refreshing to see such a thoughtfully structured and developer-friendly approach to building API clients.
While reviewing potential improvements to the file or object storage layer, I came across [Apache OpenDAL](https://github.com/apache/opendal) and wanted to suggest it as a candidate worth considering.
Why OpenDAL?
OpenDAL provides a unified interface for accessing various storage backends, including local filesystems, S3, GCS, Azure Blob Storage, HDFS, and many more — all through a consistent API. What makes it particularly compelling is:
Unified abstraction: You write your logic once and can switch between backends with minimal change.
Performance & safety: It’s written in Rust, with bindings available for Go via FFI.
Active development: The project is under active maintenance by the Apache foundation, with a growing ecosystem.
Features: Supports async operations, multipart uploads, presigned URLs, and more.
How it might benefit gigapi
If gigapi is handling any kind of object storage interaction (e.g., uploading/downloading files or managing data blobs), OpenDAL can greatly simplify backend integration and enhance portability. Even if it's not in the current roadmap, having an optional storage abstraction layer could help future-proof the architecture and improve testability by mocking against a single interface.
Of course, I fully respect the direction and philosophy of gigapi — this is just a suggestion offered in the spirit of open collaboration. If it aligns with your goals, I’d be happy to help explore a prototype integration or gather some benchmarks.
Thanks again for your great work!
Warm regards,
Chanyub Park
The text was updated successfully, but these errors were encountered:
Hi team,
First of all, thank you for your excellent work on
gigapi
. It's refreshing to see such a thoughtfully structured and developer-friendly approach to building API clients.While reviewing potential improvements to the file or object storage layer, I came across [Apache OpenDAL](https://github.com/apache/opendal) and wanted to suggest it as a candidate worth considering.
Why OpenDAL?
OpenDAL provides a unified interface for accessing various storage backends, including local filesystems, S3, GCS, Azure Blob Storage, HDFS, and many more — all through a consistent API. What makes it particularly compelling is:
How it might benefit gigapi
If
gigapi
is handling any kind of object storage interaction (e.g., uploading/downloading files or managing data blobs), OpenDAL can greatly simplify backend integration and enhance portability. Even if it's not in the current roadmap, having an optional storage abstraction layer could help future-proof the architecture and improve testability by mocking against a single interface.Here’s their Go binding repo for reference:
👉 [opendal/bindings/go](https://github.com/apache/opendal/tree/main/bindings/go)
Of course, I fully respect the direction and philosophy of
gigapi
— this is just a suggestion offered in the spirit of open collaboration. If it aligns with your goals, I’d be happy to help explore a prototype integration or gather some benchmarks.Thanks again for your great work!
Warm regards,
Chanyub Park
The text was updated successfully, but these errors were encountered: