← All Talks
◆ Past
▾ What
Migrations that never roll back
Event
Go Meetup 26 in Prague ↗
Brief
Why we left golang-migrate and built a small migration service on jackc/tern: migrations ship ahead of the code, forward only, so the service can always be rolled back.
Abstract / Notes
Why build your own database migration tool when so many exist? Our Go services ran golang-migrate at start-up, which tied the schema to the binary and made rollbacks unsafe. This talk covers the rule we adopted instead (migrations ship first and never roll back), the service we built on jackc/tern to enforce it, and the trade-offs of building against adopting.
Media
Resources