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

Doc to compare jobs vs SchemaHero #49

Open
marccampbell opened this issue Feb 6, 2021 · 0 comments
Open

Doc to compare jobs vs SchemaHero #49

marccampbell opened this issue Feb 6, 2021 · 0 comments

Comments

@marccampbell
Copy link
Collaborator

The default choice to write and deploy database migrations in Kubernetes is to wrap them in a Job. This approach has some drawbacks, and SchemaHero docs could explain this to help show the value in the operator approach.

  • Transparency in debugging
  • Sequencing
  • Tightly coupling database migrations with an app migration
  • ???
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
No milestone
Development

No branches or pull requests
1 participant
@marccampbell