1d ago · 12 min read · If you have used IBM's fp-go library, you know the promise of functional programming in Go -- and the pain of Go's syntax fighting you every step of the way. Pipe3, Pipe5, Pipe7. Function adapters eve
ASunil commented18h ago · 7 min read · Production APIs demand bulletproof error handling. While Go's explicit error handling gets you started, building resilient systems requires sophisticated patterns that go far beyond basic if err != nil checks. This guide covers advanced error handlin...
Join discussion
1d ago · 11 min read · Go is a language built on simplicity. But simplicity has costs, and one cost Go developers feel acutely is the lack of pattern matching and algebraic data types. If you have ever modeled a closed set
Join discussion
1d ago · 9 min read · Distributed systems fail. Networks drop packets, services become unavailable, and databases timeout. The question isn't whether failures will happen—it's how your Go microservices will handle them when they do. Traditional error handling patterns tha...
Join discussion
2d 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 discussion2d 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 discussion2d 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 discussion
