I didn't want to have ORMs configured just to make database migrations easier to deal with. I love golang's multi platform support and so I made a tiny SQL migration tool, ~800 LOC that will track and migrate your database changes as your application grows in complexity.
Show HN: Tiny Golang CLI tool to manage SQL migrations | Better HN
What happens if multiple migrator instances run the same migration? Imagine case when k8s or something start several instances of migrator at the same time
