18h ago · 10 min read · Encore is a fantastic framework for building Go backend applications. Its opinionated approach to infrastructure, service discovery, and pub/sub makes it a joy to develop with. But when it comes to se
Join discussion9h ago · 2 min read · Protocol Buffers + Buf CLI reference — the modern way to build typed APIs. Why protobuf over JSON for APIs? 3-10x smaller on the wire. 5-10x faster to parse. Strongly typed schema with generated code for every language. Schema evolution with backward...
Join discussion10h ago · 2 min read · Temporal reference — durable execution: workflows that survive failures, restarts, and months of running. The key mental model Workflow code = deterministic state machine (no I/O, no random, no time.Now()). Activity code = all the side-effectful work...
Join discussion10h ago · 2 min read · OpenTofu reference — drop-in Terraform replacement, now with native state encryption and built-in testing. Migration is usually trivial If you're using Terraform Open Source, switching to OpenTofu is mostly changing the binary. Your .tf files don't n...
Join discussion11h ago · 1 min read · Makefile patterns for software projects that aren't C. Tab vs spaces: the eternal gotcha # WRONG (spaces): build: go build ./... # RIGHT (tab): build: go build ./... Makefile:N: *** missing separator. Stop. means spaces where a tab should b...
Join discussion12h ago · 1 min read · gRPC patterns that aren't obvious from the official docs. Always embed UnimplementedXxx in Go servers type UserServer struct { usersv1.UnimplementedUserServiceServer // forward-compat db *DB } Without this, adding a new RPC method to the p...
Join discussion16h ago · 2 min read · Go patterns — the idioms that make Go code actually idiomatic. Error wrapping — context without losing the original // fmt.Errorf with %w wraps for errors.Is and errors.As func getUser(id int) (*User, error) { user, err := db.Query(id) if err...
Join discussion22h ago · 9 min read · Distributed systems fail. Networks partition, services go down, and databases become unavailable. The question isn't whether your Go microservices will encounter errors—it's how gracefully they'll handle them when they do. Traditional error handling ...
Join discussion