Skip to content

[server] Start the server as a Fx application #6793

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

Merged
merged 3 commits into from
Apr 10, 2025

Conversation

3vilhamster
Copy link
Contributor

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

Copy link
Member

@davidporter-id-au davidporter-id-au left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice, this is really good to see

@3vilhamster 3vilhamster merged commit 3b22c25 into cadence-workflow:master Apr 10, 2025
22 checks passed
@3vilhamster 3vilhamster deleted the fx-app branch April 10, 2025 14:43
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 this pull request may close these issues.

2 participants