About

Backend systems, incident timelines, and tradeoffs that show up after real traffic starts.

Most of my work is Node.js and NestJS services that move data across queues, databases, and APIs. Kafka consumer behavior, retry semantics, and idempotency usually matter more than feature velocity.

I spend a lot of time in PostgreSQL-heavy systems where query plans and index decisions directly impact user-facing latency. Redis-backed workflows and Dockerized environments help keep behavior predictable between local work and production.

This site documents debugging paths, architecture decisions, and operational constraints from running distributed backend systems — not motivational filler.

Experience

Inavitas

Full Stack Developer

Backend-focused full-stack work on energy-domain platforms including OMS/DMS.
Node.js, PostgreSQL/PostGIS, Redis/RedisGraph, Kafka, Docker, CI/CD, React, Nx monorepo, and microfrontend architecture.
Maintainability, service communication, production debugging, and reliability-oriented backend development.

Previous Experience — RPA / IoT / JavaScript

Early professional work across RPA, IoT, JavaScript interfaces, and product-oriented software delivery.
Automation, device-oriented systems, and frontend/backend coordination.

What I Usually Work On

Kafka consumer lag, retries, and delivery guarantees
Outbox/event-publishing consistency in NestJS services
PostgreSQL query plans and index tradeoffs under load
Redis-backed orchestration and cache correctness
Production debugging with metrics, logs, and traces
Service boundaries across backend and frontend teams