[server] Start the server as a Fx application #6793
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Onboarding server start to usage of fx.
Why?
Using go.uber.org/fx as a dependency injecvtion allows to simplify initialization of components and help establishing components boundaries. As a long term goal - we should eliminate resource package and rely on fx to connect components. Also, separate optional from mandatory components to simplify service customizations.
It is required for reusable components and allows extraction of components, such as Shard distributor, into a separate repo/internal monorepo.
How did you test it?
Unit/integration tests
Potential risks
None
Release notes
Start migration to Dependency injection using go.uber.org/fx
Documentation Changes