Why delete the Apollo config center?

[xuzhijvn]

I don't understand why the Apollo config center is deleted? As an RPC framework, isn't it a good thing to support more config centers? Just asking, what level of questionnaire is 1928

If Apollo Config Center is no longer supported, what are the recommendations for its users? Would the only option be for users to implement Apollo themselves and maintain a private package?

[AlexStocks]

Hi @xuzhijvn , thank you for your attention to dubbogo. As a service-govern framework, dubbogo supports so many third-party middleware before which leads to a large maintenance burden for our community. If you really need it in your com, we can have a talk continuously in this issue.

[xuzhijvn]

I agree with your perspective—supporting too many third-party middleware does require substantial effort. While I don't have exact statistics, I believe there is still a significant number of existing users using Apollo as their configuration center, particularly those with Java-based tech stacks. During their transition (e.g., migrating from Dubbo Java to Dubbo Go), Apollo support would help reduce migration costs. Even if they eventually switch to another configuration center, this would still be a gradual process. Therefore, I believe Apollo support in dubbogo would be highly valuable for such users. I’d be very willing to contribute this part of the code, if you also think it would be valuable.

[AlexStocks]

@xuzhijvn If so, your PR and contribution will be welcome. Thank you again in the name of dubbogo community.

[xuzhijvn]

Roger that. I'll submit it shortly. Please let me know if you have any suggestions.

[AlexStocks]

Roger that. I'll submit it shortly. Please let me know if you have any suggestions.

Just do it. Thx agagin.