100 challenges to take you from `go version` to shipping a production Go service with OTel, structured logs, graceful shutdown, and a Docker image small enough to fit in a tweet.
Go is the language of cloud infrastructure (Kubernetes, Docker, Terraform, etcd). This course is a top-to-bottom build of Go competence: toolchain, types, concurrency, stdlib I/O, testing, project layout, Postgres, HTTP servers, background workers, and full production architecture. Module 1 is fully authored and free; Modules 2–10 are being authored and currently land as stubs. The capstone is a real URL shortener with chi, pgx, Redis, asynq, OTel, and a docker-compose so a reviewer runs it in one command.
Built by Lakshya Kumar
Paste this into any AI chat. Fill in the bracketed parts with your context — you'll get back a straight answer on whether this belongs on your plate.
We grant free access case-by-case — students, career-switchers, builders on a tight budget. Sign in to send us a note.
Sign in to applyComplete all modules, then submit the required number of capstone projects. Each must earn a passing rating from an admin reviewer.
Build `linkr`, a URL shortener service in Go. Required: chi router, pgx + Postgres for link storage, Redis for hot-cache and rate-limiting, an asynq worker that sweeps expired links and aggregates click analytics, OTel traces, Prometheus `/metrics`, structured `log/slog` JSON logs, graceful SIGTERM shutdown that drains in-flight redirects, and a `docker-compose.yml` that brings up the whole stack in one command. Submit: the repo URL, a Loom or asciinema of the docker-compose start-to-redirect flow, and a load-test (`oha` or `wrk`) showing p95 redirect latency under 5 ms cached.
I'm considering Capstok's "Go: From Zero to Production Service" course. It covers the toolchain, types and interfaces, goroutines + channels + context, stdlib I/O, testing, project layout, Postgres with pgx, HTTP servers with chi, background workers, and full production architecture (OTel, slog, Docker). Capstone is a URL shortener. Context about me: 1. My current role/focus: [e.g. "Python backend dev", "frontend engineer crossing over", "self-taught"] 2. The closest I've come to Go before: [e.g. "never written it", "tutorials only", "small CLI"] 3. What I want to be able to do at the end: [e.g. "ship a Go service at work", "pass a Go interview", "write Kubernetes operators"] Answer: - For my background, which 2 modules will pay back fastest in the next 3 months and why? - A concrete bug I'm likely to ship in my first Go service that this course would catch. - Is 45 hours worth it for me, or should I learn TS/Python deeper first? Honest pick. - What this course explicitly will NOT teach me (e.g. Kubernetes ops, gRPC internals)?
The book. Pre-generics but every concept is still current.