Go

gRPC vs REST: when I actually reach for each (and when gRPC is a mistake)

gRPC vs REST gets argued in the abstract. I've shipped both — a Rails↔Go deploy engine on gRPC, browser uploads on plain WebSockets. Here's my actual rule for choosing, and the cases where gRPC is the wrong call.

Streaming a deploy from a Go agent to Rails over gRPC

One-click deploy means running git clone, docker build and docker run on a remote box and showing every log line live. How I stream that: a Go agent that pipes each command's output over a gRPC server-stream to a Rails control plane, which turns it into a live deploy log.

Streaming uploads over WebSockets in Go with io.Pipe backpressure

A browser MediaRecorder emits video chunks for minutes on end. Buffering each recording in RAM doesn't scale. How I stream chunks straight to storage over a WebSocket in Go, using io.Pipe so the socket buffer becomes the backpressure.