dubbo-api-docs Pre-research and plan writing based on Dubbo SPI reconstruction
dubbo-api-docs is currently based on Spring's annotations on scanning docs, and the scan results are cached in memory. You need to use Dubbo's SPI mechanism to intervene in the scan, and put the scan results in the metadata center. And no longer provide the docs self-use provider, Admin directly obtains data from the metadata center. It is necessary to investigate whether there is a suitable SPI in Dubbo (the priority is to investigate whether there is a suitable SPI when Dubbo scans metadata) to intervene in scanning, and how to add metadata to the metadata center. (Add attributes to existing metadata or store them separately)
Project requirements:
- Refactored concrete realization plan
- Refactored POC
Skills requirement:
- Proficiency in Java
dubbo-api-docs 目前是基于 Spring 扫描 docs 相关注解的,并且扫描结果缓存在内存中。需要改为以 Dubbo 的 SPI 机制介入扫描,并把扫描结果放到元数据中心. 并且不再提供 docs 自用的 provider, Admin 直接从元数据中心获取数据。需要调研 Dubbo 中有没有合适的SPI (优先调研 Dubbo 扫描元数据的时机有没有合适的SPI )以介入扫描,以及如何向元数据中心中增加元数据。(在现有元数据中增加属性,还是单独存放)
产出要求:
- 重构的具体实现方案
- 重构的 POC
技术要求:
- 熟练使用 Java