Predictable under load
Latency budgets, back-pressure and load tests come before the launch, not after the incident.
Backend Developer
Vlamirov
I build the systems nobody sees — and everybody feels.
3+ years building real-time backends
Architecture in motion
- 01
It starts with people.
Web, mobile, desktop — thousands of clients, each sending a stream of small, impatient requests.
- 02
One door in.
A gateway authenticates, rate-limits and routes traffic before it reaches anything that matters.
- 03
Services that talk, not wait.
Small services call each other when they need an answer now — and publish events when they don't. NATS, Kafka, RabbitMQ: the bus fits the job, not the other way around.
- 04
Real time, for real.
Live state goes straight back to clients over WebSockets. Milliseconds, not page reloads.
- 05
The right store for each job.
PostgreSQL for truth, ClickHouse for history, Redis for speed, object storage for files — and vectors and search where they belong.
- 06
Quietly, all the time.
Every hop is measured, logged and traced. When it works, nobody notices. That is the whole point.
How I work
Observable by default
Every service explains itself with metrics, traces and errors you can actually act on.
Boring infrastructure
Proven tools, simple deploys, reproducible environments. Excitement belongs in the product.
Data tells the truth
Decisions follow numbers: user behaviour, product metrics, performance regressions.
Toolbox
The tools I reach for every day — and the ones I pick up when a project needs them.
- Python
- TypeScript
- React
- Three.js
- PostgreSQL
- ClickHouse
- Redis
- NATS
- Kafka
- RabbitMQ
- Docker
- GitLab CI
Let’s talk.
Have a project, a question or just want to compare notes on backend architecture? Write me.
vladamirov1980@gmail.com