Sergey / Go backend engineer

Building reliable
systems.
Engineering
for scale.

I’m Sergey, a Go backend engineer focused on distributed systems, event-driven architecture, and cloud infrastructure.

Get in touch
eventforge / system map

Follow the event.

One system. More than a happy path.

PostgreSQL1 / 5

One transaction writes the order and its outbox event. Either both commit, or neither does.

Illustrative model · select a nodeat-least-once

A small window into how I think about systems.

GoPostgreSQLKafkagRPCCloud
Scroll to the work

Selected engineering work

Three perspectives on backend engineering: an experiment, a learning system, and professional practice.

All projects
Engineering approach

Reliability is a series of decisions.

The interesting part is rarely the happy path. It’s what happens when a request times out, an event arrives twice, or a dependency becomes unavailable.

Make failure explicit.

Delivery semantics, idempotency, bounded retries. Recovery belongs in the design, not in a runbook written after an incident.

Measure before changing.

Profiles, traces, and a reproducible workload. Understand the bottleneck before choosing the optimization.

Keep the system understandable.

Small interfaces, clear ownership, and operational simplicity. A system should be easy to reason about when it matters most.

Technical focus

The tools follow the problem.

Go at the core. Clear contracts between services. Enough observability to understand what happens in between.

Services & interfaces
Go / REST / gRPC
Data & messaging
PostgreSQL / Redis / Kafka / NATS
Infrastructure
Docker / Linux / GCP / CI/CD
Observability
OpenTelemetry / Prometheus / Grafana
Professional experience

Behind the interfaces, real engineering.

Backend services for voice and ML workflows: streaming interfaces, asynchronous processing, and integrations between services.

Read about the work
ZuzexBackend developerVoice & ML systemsgRPC / async / observability
Let’s talk

Good systems start with a conversation.

Interested in backend engineering, distributed systems, or a thoughtful technical collaboration?

Write an emailbxmbuksss@gmail.com