Dubbo GSoC 2023 - API manager
- Dominant language
- Java
- Stars
- 41.6k
- Forks
- 26.4k
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 4
Description
Since Dubbo runs on a distributed architecture, it naturally has the problem of difficult API interface definition management. It is often difficult for us to know which interface is running in the production environment. So we can provide an API-defined reporting platform, and even a management platform. This platform can automatically collect all APIs of the cluster, or can be directly defined by the user, and then unified distribution management is carried out through a mechanism similar to git and maven package management.
https://issues.apache.org/jira/browse/DUBBO-121
Contributor guide
Research direction
Start with the linked DUBBO-121 design and review how Dubbo currently exposes and manages APIs across a cluster. Define the scope for API collection, user-defined APIs, and unified distribution management before locating implementation entry points. Done means an agreed API reporting and management platform is implemented for the stated use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100