A cloud-native platform running in production on AWS. Below is the real architecture we operate today — not a roadmap slide.
Next.js storefront with a three-tier package model (Standard / Premium / Custom-fit), server-authoritative pricing (room × night computation, per-guest ride allocation, seasonal monthly rates, daily premium quotas with race-safe counters), discount campaigns and a lucky-draw promotion engine. Every price is re-computed server-side at checkout — the client is never trusted.
A Model Context Protocol server exposes 36 guarded tour-management tools — package pricing, room configuration, itinerary presets, content briefs — so operators can manage their catalog conversationally through AI assistants, with token-based auth, validation and change-tracking on every write.
Dual-database draft/publish pipeline with field-level change tracking, batch publish queue, compressed snapshots and 7-day rollback. Block-based blog editor, media library on S3, structured data (JSON-LD) tuned for search engines and AI answer engines.
Real-time chat service (Socket.io + REST persistence) unifying website, Facebook Messenger and WhatsApp conversations with cross-platform identity linking, agent assignment and full audit history.
Express + PostgreSQL booking-lifecycle system: automatic price recalculation, accommodation/transport/surcharge management, tokenized payment links, gateway integration, PDF receipts, CSV/Excel exports, role-based access and audit logging.
Serverless email pipeline (SQS FIFO → Lambda → SendGrid/SES) with delivery tracking and dead-letter handling; scheduled Lambda jobs publish daily pickup reminders to operations staff.
Elastic Beanstalk & CloudFront (storefront), Amplify (backoffice apps), Lambda + API Gateway (public APIs, payments, notifications), RDS PostgreSQL, EC2 (real-time messaging), S3, SQS/SNS, SES, Route 53.