The core problem is that your largest customer, Northwind Logistics, spikes their traffic beyond their contracted Requests Per Minute (RPM) between 02:00-04:00 UTC. You must resolve conflicting stakeholder instructions explicitly and ensure the system behaves correctly at the boundary conditions.

(Explaining the Project): "My flight booking platform is a containerized application designed to handle high-concurrency reservations. Rather than a basic CRUD app, I built a transactional system featuring a custom digital wallet (Wallet.js) for user balances and a dedicated PricingLog.js architecture to track volatile fare changes and maintain an immutable audit trail. The entire environment is orchestrated with Docker Compose to ensure strict parity across deployment stages."

AI Interviewer (The Interruption): "I notice you built this transactional and financial ecosystem using the MERN stack (MongoDB, Express, React, Node.js). Relational databases like PostgreSQL are traditionally preferred for financial ledgers due to strict ACID compliance. Why did you choose MongoDB for a platform handling digital wallet deductions and concurrent seat inventory?"

(Defending the Tech Stack): "That is a great callout. While PostgreSQL is the gold standard for traditional ledgers, I deliberately chose Node.js and MongoDB for two specific reasons:

Asynchronous I/O for Read-Heavy Traffic: A flight platform is heavily skewed toward reads (searches) versus writes (bookings). Node's event-driven architecture handles thousands of concurrent search requests without thread-blocking.