Systems

Systems

Architecture decisions as a whole, and the reasoning behind them.

  1. Race Conditions and Gaps in Sequential Numbering: JIT Reservation

    Generating legally sequential, gap-free numbers with parallel workers: the JIT reservation pattern that solves race conditions and gaps together

  2. Scale Breaking Points in Data-Intensive Systems

    As data load grows, where does boring architecture break? Working set, read replicas, partitioning, write load and a separate data layer — the breaking points in order, and what each one costs

  3. Multiple Projects on a Single VPS

    One VPS, several independent apps. Deliberate minimalism over Kubernetes: user isolation, separate PHP-FPM pools, shared PostgreSQL/Redis, a plain deploy.

  4. Laravel Production Stack

    A production-grade Laravel setup with Nginx + PHP-FPM + Redis + PostgreSQL + Supervisor + Horizon. Each piece job and what you lose if you drop it