Apache OpenDAL 2025 Roadmap: Perfecting Production Adoption

[Xuanwo]

We have shared our 2025 roadmap. Feel free to discuss it here.

This issue is intended to track the progress of our 2025 roadmap. Here, we will gather tracking issues for various detailed goals and provide our community with an overview of our progress.

Feel free to join the discussion on GitHub issues or in our Discord: https://opendal.apache.org/discord

---

OpenDAL 2025 Goal: Perfecting Production Adoption

Features Needed in Production

Core

New features in 2025:

• context: Tracking issues of RFC-5479: Context #5480 (good first issues)
• versiong: Tracking issues of RFC: Object Versioning #2611
• checksum: new feature: Checksum #5549
• caching: new feature: Add cache layer for opendal #5678
• init_from_uri: Allow init Operator via URI #3022

Not finished in 2024:

• Tracking Issues of RFC-5556: Write Returns Metadata #5557 (good first issues)
• Tracking Issues of RFC-5495: List With Deleted #5496
• Tracking issues of RFC-5485: Conditional Reader #5486 (good first issues)
• Tracking issues of user metadata support #4842
• Tracking issues of Completion Based IO #4520
• Tracking issues of RFC-3911: Deleter API #3922
• Tracking issues of OpenDAL wasm32-unknown-unknown target support #3803
• new feature: Returning metadata while reading #5425

Bindings

• dart: Tracking Issue: dart binding examples, tests, docs && publish #5722
• golang: Tracking issues of golang binding #4892
• cpp: Tracking issues of cpp binding #2981
• c: Tracking issue of missing functionalities in OpenDAL C binding #2959
• php: Tracking issuss of Bindings PHP #2813
• ocaml: Tracking issues of OCaml binding #2756
• swift: Tracking issues of Swift binding #2476
• lua: Tracking issues of Lua binding #2474

Integrations

• Tracking issues of spring integrations #5015
• Tracking issues of integration virtiofs #4786

Applications

• Tracking issues of goal: Make ofs running! #3782

Improvements Needed for Production

• Code Refactor
  • Tracking issue: Refactor services to use the backend.rs and core.rs convention #5702 (good first issues)
  • Tracking issues of migrating adapter based services #5739
  • Tracking issues of QueryPairsWriter refactor #5976 (good first issues)
• Documentation
  • Add docs for High Performance OpenDAL  #4121
• Communitation

[meteorgan]

So many interesting issues ! We need to improve the content of tracking issues of RFC: Object Versioning #2611 as some tasks aren't included. And should we include Returning metadata while reading: #5425 ?

[Xuanwo]

So many interesting issues ! We need to improve the content of tracking issues of RFC: Object Versioning #2611 as some tasks aren't included. And should we include Returning metadata while reading: #5425 ?

Makes sense, I have updated.

[erickguan]

What do you think about adding documentation about service configurations?

I propose:

• Add a "Services" section on the website.
  
• Populate each service’s documentation from docs.md.
• Move Rust builder-related code to each builder.

Advantages:

• Enhanced Visibility: Developers can quickly understand which features each service supports.

• Consistent Convention: Provides a simple, uniform approach for writing docs.md.

• Cross-Linking: Bindings documentation can easily link to the services documentation, improving navigation and context.

Disadvantages:

• Fragmentation: There’s a risk of documentation being split between a central services section and language-specific bindings, which might lead to inconsistencies.

• Maintenance Overhead: Keeping the services documentation up to date in both the central section and within bindings might require extra effort.

• Indirection Complexity: If we choose not to include service documentation in bindings, we will add an extra layer of indirection. The indirection could make navigation more confusing if not managed properly.

Open Questions:

• How should a binding’s documentation incorporate the services documentation?

• Will the added indirection cause usability or navigation issues?