Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] 配置中心服务 #808

Closed
3 tasks done
Tracked by #747
wibus-wee opened this issue Jun 20, 2023 · 0 comments · Fixed by #844
Closed
3 tasks done
Tracked by #747

[Feature] 配置中心服务 #808

wibus-wee opened this issue Jun 20, 2023 · 0 comments · Fixed by #844
Assignees

Comments

@wibus-wee
Copy link
Member

wibus-wee commented Jun 20, 2023

BREAKING CHANGE

This PR will transfer all of the service's modified configuration logic to a separate configuration service.

That is, when this PR is merged, the configuration of all services will be centrally managed, and the original ConfigService Library will be completely removed.

Why?

Abstract the ConfigService into a library, which is great in a single application scenario (see "全栈之巅").

However, the problem is that this is a microservice application.

If each service is created with the ConfigService database, it is difficult to manage data in a unified manner. Import, export, and migration operations are difficult and inefficient.

Therefore, it is necessary to build an additional Config Microservice

Tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant