Skip to content

Work

Systems, interfaces, and the decisions between them.

Real projects, client names withheld. Each entry covers the constraint, the architecture, and the decisions that kept the system dependable.

01

Case study · Agritech commerce

Document-Gated Commerce Platform

One modular-monolith backend serves web, mobile, field-sales, and admin clients. Purchases that need identity and land paperwork pass AI-assisted verification before payment; stock is decremented under row locks, a worker reconciles payments, and chat scales across instances through Redis.

Modular monolith · AI document checks · GCP + Terraform

02

Case study · Tourism booking

Inventory-Safe Reservation Platform

Tickets, stays, timed activities, and packages share one cart and one checkout. A serializable transaction reserves stock all-or-nothing with 15-minute holds, an idempotent payment service owns every provider call, and RabbitMQ events feed separate audit and analytics services.

Event-driven services · Payments · Infrastructure as code

03

Case study · Professional services

Serverless Bilingual Advisory Site

A bilingual content and lead-intake site with no backend server. Firestore rules mirror the client's Zod schemas as the validation layer, App Check guards every read, and a build-time Puppeteer prerender with a generated sitemap makes the static SPA indexable.

Serverless · SEO prerendering · Security rules

Case study anatomy

Evidence over spectacle.

01

Context

What changed, who was affected, and why the problem mattered.

02

Constraints

The technical, product, and operational limits shaping the work.

03

Decisions

The alternatives considered and the trade-offs behind the chosen path.

04

Outcome

What improved, what remained unresolved, and what was learned.

Next conversation

Have a difficult problem worth making simpler?

Tell me what you are working on. I will reply to the email address you provide.

Your email is used only to reply to this message.