FuncWarm
A warmup control plane for serverless environments.
I’m Sergey, a Go backend engineer focused on distributed systems, event-driven architecture, and cloud infrastructure.
Get in touchOne system. More than a happy path.
One transaction writes the order and its outbox event. Either both commit, or neither does.
A small window into how I think about systems.
Three perspectives on backend engineering: an experiment, a learning system, and professional practice.
A warmup control plane for serverless environments.
An order-processing system built around delivery guarantees.
Backend interfaces between voice workflows and ML services.
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.
Delivery semantics, idempotency, bounded retries. Recovery belongs in the design, not in a runbook written after an incident.
Profiles, traces, and a reproducible workload. Understand the bottleneck before choosing the optimization.
Small interfaces, clear ownership, and operational simplicity. A system should be easy to reason about when it matters most.
Go at the core. Clear contracts between services. Enough observability to understand what happens in between.
Backend services for voice and ML workflows: streaming interfaces, asynchronous processing, and integrations between services.
Read about the workInterested in backend engineering, distributed systems, or a thoughtful technical collaboration?
Write an emailbxmbuksss@gmail.com