Go in Production covers: Writing An Interpreter In Go, Build Web Application with Golang, Go Web Development Cookbook, Go Building Web Applications. Build production-quality Go web services. Testing, APIs, databases, deployment.
| Rails | Go |
|-------|-----|
| rails new myapp | mkdir myapp && go mod init — no generators, no magic |
| config/routes.rb | http.HandleFunc or a router like chi/gorilla |
| ActiveRecord | database/sql + raw SQL (or sqlx/GORM) |
| RSpec / Minitest | testing package, go test, table-driven tests |
| rails server | http.ListenAndServe — your server, your responsibility |
| Puma (multi-process) | Single binary, goroutines handle concurrency |
| Dockerfile (multi-stage) | Same, but Go produces a single static binary (~10MB vs ~500MB Rails image) |
This course unlocks once you've finished its prerequisite. Open prerequisite →
Writing An Interpreter In Go by Thorsten Ball is a brilliant curriculum choice, and I want to be clear about why: it is not really about interpreters. It is about how a skilled Go…
Here is a strange fact about learning Go: the best book about building production-quality Go projects is not a web book, not a microservices book, not a cookbook. It is a book abo…
Somewhere in your first week of Go web work, you will type the equivalent of params.require(:user).permit(:email) and discover that nothing like it exists. No strong parameters. N…
There is a moment in every first production Go service — usually around the third middleware — where you stop asking "how does Go work?" and start asking "how do people usually do…
The last book of a course has a different job than the first. You are no longer learning Go web development — three books and most of a checkpoint in, you do Go web development. S…
Work through each item before the checkpoint.
A production-shaped REST API in (almost) pure standard library: the middleware stack Rails gives you for free — request logging, panic recovery, auth — rebuilt by hand, plus grace…
7 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.