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

Managing Data Migration #60

Open
vigneshhari opened this issue Oct 3, 2024 · 0 comments
Open

Managing Data Migration #60

vigneshhari opened this issue Oct 3, 2024 · 0 comments

Comments

@vigneshhari
Copy link
Member

Create a best practice doc for migrations that involve structural and data changes.

Edge Cases to think about. -

  • Deployments are not always performed by the core team, migrations should be self-sufficient in the sense that it should not need any external changes
  • Deployments need not happen in sync with development, Deployments for some instances might happen only once in a quarter, which other instances might deploy every week. We need to understand how this impacts migrations and work around them to avoid downtime in critical systems.
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

No branches or pull requests

1 participant