Self maintianed SDK

[Xuanwo]

Normally, it's a bad idea. But maybe it's deserved for opendal.

Benefits

• Underlying control over HTTP and its connection pool.
• OpenDAL only needs a small part features of SDK.
• OpenDAL needs a unified logic for retry and timeout (across different services).
• Smaller dependences tree, faster build time.
• Easier to support more services without formally native SDK support (all services except s3).

Drawbacks

• (a lot) extra works.
• maybe buggy.

---

Take aws-s3-sdk as example, to make s3 works, we need:

aws-config = "0.8"
aws-endpoint = "0.8"
aws-http = "0.8"
aws-sdk-s3 = "0.8"
aws-sig-auth = "0.8"
aws-sigv4 = "0.8"
aws-smithy-client = "0.38"
aws-smithy-http = "0.38"
aws-smithy-http-tower = "0.38"
aws-types = { version = "0.8", features = ["hardcoded-credentials"] }

And we only use five APIs:

• put_object
• get_object
• list_objects
• delete_object
• head_object

Apart from s3's signing logic, s3 API is quite simple:

• put_object -> PUT /abc/def
• get_object -> GET /abc/def

It's not a big burden to maintain those APIs.

[Xuanwo]

Powered by https://github.com/Xuanwo/reqsign