E-commerce Logistics
Facilitating rapid air transport and international delivery to Algeria with seamless logistics for businesses and individuals.
View Live ProjectDuration
4 months
Role
Lead Full-Stack Engineer
Team
Senior Software Engineer, QA Engineer
Overview
A specialized booking interface built for a luxury beach resort, enabling direct reservations without relying on third-party OTAs. The platform handles real-time room availability, dynamic pricing rules, and PCI-compliant payment processing — all from a single admin dashboard.
Problem & Solution
The Challenge
The resort was losing 18–22% of each booking to OTA commission fees and had zero visibility into guest data. Their existing system couldn't handle concurrent booking conflicts, leading to double-bookings during peak season. Staff were manually reconciling availability in a spreadsheet updated three times a day.
The Engineering Solution
Designed a CQRS-based reservation engine with an event-sourced availability ledger, ensuring every booking mutation is atomic and conflict-free. Integrated Stripe with 3D Secure and implemented a webhook pipeline that syncs payment state in real time. A Nuxt 3 frontend with SSR reduced initial load time to under 800 ms even on mobile connections.
Engineering Deep Dive
The hardest part was designing the concurrency model. Two guests could simultaneously reach the payment screen for the last available room. I solved this with a two-phase reservation lock: a provisional hold for 12 minutes (TTL-backed in Redis) that converts to a confirmed booking only after payment capture. This eliminated double-bookings entirely without requiring distributed transactions.
Technology Stack
Gallery
Impact & Results
Within 60 days of launch the resort redirected 40% of bookings to the direct channel, saving an estimated $28,000 in OTA commissions over the first quarter. Average booking completion time dropped from 6 minutes (OTA flow) to 2.3 minutes. The platform handled a 3× traffic surge during a promotional campaign with zero downtime.
Key Learnings
“Building a reservation system taught me that the biggest risk isn't bad code — it's unclear ownership of business rules. Spending the first two weeks writing rigorous domain specs (ubiquitous language, bounded contexts) paid off enormously: every developer could reason about availability state without reading source code.”