Backend development in Go: REST/gRPC API, microservices, high load

I develop high-performance backends in Go and focus on services that remain fast and predictable under real battle load. Behind me — REST and gRPC APIs, pools of concurrent workers, queue consumers and background pipelines that process millions of events without memory leaks and without growing latency. Taking on a task, you get an engineer who from the first commit thinks about goroutine lifecycle, context cancellation, backpressure and graceful shutdown, not when everything starts falling apart.

The typical result of my work is clean, neatly structured service: layered architecture, clear domain boundaries and dependency injection only where it's justified. I write unit and integration tests, connect structured logs, metrics and tracing, pack everything in Docker so the service runs the same on a laptop and in a cluster. I watch for memory efficiency and low garbage collector load, so infrastructure costs stay small and p99 stays flat even at traffic peaks.

I can start a project from an empty repository or connect to existing code: I profile slow spots and rewrite them into maintainable form. Tell me about target throughput, data stores and timeline — I'll suggest a realistic plan and hand over working, observable code you can trust in production.