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.

Sign up for GitHub

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

Jump to bottom

Reconsider when EF schema migrations are applied #11

Open
adityamandaleeka opened this issue Nov 1, 2023 · 1 comment
Open

Reconsider when EF schema migrations are applied #11

adityamandaleeka opened this issue Nov 1, 2023 · 1 comment
Milestone
Backlog

Comments

@adityamandaleeka
Copy link
Member

From @bricelam

Today, database schema migrations are applied as certain components start up. This is problematic when multiple components (or multiple instances of the same component) use the same database.

Currently, for example, Ordering.BackgroundTasks immediately begins querying the OrderingDB database. This continually fails while waiting for Ordering.API to create and migrate the database schema to the latest version.

Data seeding (#10) should also be done at the same time.
@adityamandaleeka adityamandaleeka added this to the Backlog milestone Apr 5, 2024
@AndriySvyryd
Copy link
Member

WaitForResourceAsync(...) can be used to fix this once implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@adityamandaleeka @ajcvickers @AndriySvyryd