I really enjoyed this article and how it highlights best practices for DB migrations! I fully agree with the migrations-based approach as opposed to the state-based one, but as you've pointed out, without some tooling and automation around this, it can become extremely tedious (and error-prone as a project becomes more complex)!
I work at Prisma and we've recently launched a tool called Lift that picks up the migration-based approach and tries to support it with proper tooling. I'd love to hear what you think of it and how it its into your mental model of DB migration approaches!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I really enjoyed this article and how it highlights best practices for DB migrations! I fully agree with the migrations-based approach as opposed to the state-based one, but as you've pointed out, without some tooling and automation around this, it can become extremely tedious (and error-prone as a project becomes more complex)!
I work at Prisma and we've recently launched a tool called Lift that picks up the migration-based approach and tries to support it with proper tooling. I'd love to hear what you think of it and how it its into your mental model of DB migration approaches!