[System Architecture Flowchart Topology Diagram]
Nationwide vehicle inspection and modification scheduling platform managing multi-lane inspection facilities across Saudi Arabia within strict 15-minute booking blocks. Delivered across three phases over three years — initial platform build, optimization, and headless migration — with intervening work on other iSoft engagements between phases. Three independent clients (public web portal, state internal backend, mobile application) competed simultaneously for identical time slots under concurrent load. Hosted on government-subsidized third-party infrastructure; production access was restricted — all validation performed on simulated pre-production environments.
//Engineering Impact
- ->Resolved distributed booking collisions across three competing clients by designing a deterministic state-lock system: slot selection deferred validation to the final workflow step, with a 5-minute inactivity window automatically returning abandoned slots to the pool — recovering previously wasted scheduling capacity at national scale.
- ->Restructured fragmented data models into 3NF for transactional integrity combined with Star Schema for analytical read performance, reducing calendar and dropdown dataset load times to near-instant execution under peak load.
- ->Led multi-phase migration from monolithic Drupal core to decoupled headless architecture: extracted validated business logic into versioned APIs consumed by a React frontend, improving frontend deployment independence and API reuse across clients.
- ->Established project-wide engineering terminology dictionary and Jira workflow standards aligned to release calendars.
//Edge Cases Managed
- ->Three-way concurrent booking collisions: public portal, state backend, and mobile app competing for identical 15-minute slots simultaneously — solved via distributed state locking with deterministic timeout.
- ->Proxy authorization gap: system assumed vehicle owner and driver were identical; real-world usage required owners to delegate inspection appointments to third-party drivers. Implemented a portal-level proxy authorization layer to handle delegation without compromising booking integrity or owner accountability.
- ->All pre-production validation performed on simulated environments due to restricted production access — required deterministic, environment-agnostic code and rigorous pre-deployment testing discipline.
FIG. 02
[Data Isolation Node Pipeline Diagram]