Backends
that
stay up

Stock and cash accounting for a wholesale trader

Problem

A wholesale food business lives by two questions: what is in stock and what it cost, and where the money is — who owes us, which seller is holding cash, what is left after expenses. All of it in two currencies at once.

My role

Solo, full stack: Symfony API, Vue client, plus Android build via Capacitor, desktop build via Electron and receipt printing over ESC/POS. 127 test files on the API.

Hard part

Money is never a float and is never summed across currencies. Sales are allocated over batches FIFO, and four append-only ledgers record every movement — a cancellation appends the opposite row instead of editing history. Every posting path takes pessimistic locks in a fixed order, so two simultaneous requests cannot spend the same cash twice.

Backend

PHP 8.3Symfony 7.3API Platform 4Doctrine ORM 3PostgreSQL 15JWTPHPUnit

Frontend

Vue 3PiniaTailwind 4ViteCapacitorElectronESC/POS

Infra

DockerNginx

● one-click demo login

Content-planning CRM for an SMM agency

Problem

An agency runs dozens of client projects at once; every post has a format, target platforms, a deadline and an executor. Kept in chats, this falls apart: nobody sees today's plan, who is overloaded, or what is overdue.

My role

Full stack: Symfony API with real-time updates, Quasar client with kanban boards and a content calendar, three roles, PDF exports and a daily Telegram digest.

Hard part

Boards update without polling — Mercure pushes every card move over SSE to all open tabs. Heavy work such as reports and the Telegram digest goes through Messenger to Redis, so the request returns instantly and the job runs in the background.

Backend

PHP 8.2Symfony 7.4API Platform 4MariaDB 11Redis 7MercureMessengerJWT

Frontend

Vue 3Quasar 2Piniavue-i18nvuedraggablejsPDF

Infra

DockerNginxTelegram Bot API

● one-click demo login

Landing site for a 3D course

Problem

A Blender tutor needed a page that sells the course in Uzbek: what it covers, a showcase of student and author work, pricing plans and a way to enrol.

My role

Frontend: Quasar single-page app — sections with 3D renders, a YouTube portfolio gallery, pricing and a support form, with i18n.

Hard part

Layout rather than logic: a dozen YouTube embeds, a Swiper carousel and per-section 3D renders had to stay readable from a wide desktop down to a phone. Built on Quasar's responsive grid, with breakpoint-specific columns on the portfolio and pricing pages.

Frontend

Vue 3Quasar 2Piniavue-i18nSwiper

Infra

DockerNginx

Marketplace for renting cottages

Problem

Owners list cottages, guests search, save favourites and book. Both sides need the same app: a catalogue with photos and a map for guests, a cabinet with their own listings for owners.

My role

Frontend: Quasar single-page app — catalogue, cottage pages with Google Maps, favourites, owner cabinet with add/edit, auth, profile and i18n.

Hard part

A three-language interface (Uzbek, Russian, English), a cottage page with the location on Google Maps, and search filters backed by reference dictionaries — regions, districts, amenities, rental terms — each in its own Pinia store so the filters stay consistent across pages.

Frontend

Vue 3Quasar 2Piniavue-i18nGoogle Maps

Infra

DockerNginx