wait4x VS migrate

wait4x plays the same role, but is available as a versioned container and provides more services to wait for: HTTP, DNS, databases, and message queues. That's my current choice.

Wait4X is a lightweight, zero-dependency tool designed to wait for services to be ready before continuing. It's a Swiss Army knife for service readiness checks, supporting multiple protocols and integrations including TCP, HTTP, DNS, and various databases.

# ============================ # Stage 1: Builder (Shared build environment) # ============================ FROM golang:1.25.5-alpine3.21 AS builder RUN apk add --no-cache git ca-certificates curl WORKDIR /build # Copy dependencies first (cache optimization) COPY go.mod go.sum ./ RUN go mod download && go mod verify COPY . . # Static linking build ARG COMMIT=unknown ARG BUILD_TIME=unknown RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build \ -tags timetzdata \ -ldflags="-w -s -X ...app.commit=${COMMIT} -X ...app.buildTime=${BUILD_TIME}" \ -trimpath \ -o myapp \ ./cmd/myapp # Download the migrate tool ARG MIGRATE_VERSION=v4.17.1 RUN curl -L https://github.com/golang-migrate/migrate/releases/download/${MIGRATE_VERSION}/migrate.linux-amd64.tar.gz | tar xvz && \ mv migrate /usr/local/bin/migrate && \ chmod +x /usr/local/bin/migrate

Since migrations are so handy at creating a healthy way to deal with database changes, a great variety of tools exist to manage them in numerous frameworks such as Alembic for Python, migrate for Go, etc.

I used golang-migrate for database migration with Spanner, so here's a note.

//download it curl -L https://github.com/golang-migrate/migrate/releases/download/v4.17.0/migrate.linux-amd64.tar.gz | tar xvz //copy it to go path bin cp -r migrate $GOPATH/bin/migrate //if migrate command does not work //add the folliwng lines to ~./bashrc export GOPATH=$HOME/go export PATH=$PATH:$GOPATH/bin

In this boilerplate, we use golang-migrate/migrate, a production-grade migration tool that integrates well with both automation scripts and CI/CD pipelines. It helps ensure that every environment runs the same schema version — no matter where or when migrations are applied.

The great thing is that dbmate provided a matrix with other migration tools, and there I found migrate.

curl -L https://github.com/golang-migrate/migrate/releases/download/v4.17.1/migrate.linux-amd64.tar.gz | tar xvz sudo mv migrate /usr/local/bin/

Migrate is another popular choice for Go developers. It’s a CLI-first tool that supports a wide range of databases (PostgreSQL, MySQL, SQLite, etc.) and focuses on simplicity and portability. Unlike Goose, Migrate is language-agnostic, so it’s great for teams using multiple languages alongside Go.

For advanced tips, check the golang-migrate docs.