Discussion of Roadmap v0.4

[Xuanwo]

I'm expecting to release opendal v0.4 on 4/8 (in 2 weeks).

In this release, I want to include some API breakages.

New read/write APIs in Accessor

I've been working on this design for a long time (since the start of opendal itself). I think it's ready to make it public for reviewing and comments.

We will generally use stream-based read and sink-based write in Accessor instead of a Reader. In this way, we can delegate more control for our users who want to make sure async runtime only wait for IO.

Detailed information will be presented in an RFC.

Remove overdesigned Credential concept

As described in #188, Credential is overdesigned, and we nearly never use other variants. We should remove it.

Detailed information will be presented in an RFC.

---

Also, I want to bring new features.

Fully dir support

Make opendal possible to operate on dir, including mkdir and rmdir.

Detailed information will be presented in an RFC.

Add azblob and gcs support

With the help from @D2Lark, we have essential azblob support now. It's time for us to make it a bit further.

Let's extend opendal power to all significant object storage services:

• S3
• Azure Blob
• Google Cloud Storage

---

v0.4 will be a massive release for opendal. I'm excited about it!

If you have any direction of interest, welcome to communicate with me 🚀

[BohuTANG]

Glad to see the plan : exciting
From the user side, I will care more about the improvement&stable with the s3 we have supported rather than supporting the new GCS storage(If it's easy to do, welcomed).
I would like to suggest one feature for v0.4:
#70

This feature will make user life easy again who have many small zip files on the s3 and want to load into databend.