Loading...
Loading...
Browse 4 real-world technical and behavioral interview questions about Order management. Review scenarios, edge cases, and architectural best practices.
Model the journey as milestone events, each carrying both the time it happened and the time you recorded it, and derive current status by projecting that set in a fixed milestone order rather than storing a mutable column, because events arrive late, twice and in the wrong sequence.
The split forces order, shipment and parcel apart as separate entities with their own promises, money and tracking, so a single order status stops being expressible. Model the promise per line, capture funds per despatch, and give the customer a page that reads as one order made of several deliveries.
The order is decomposed against the product catalogue into technical tasks on separate systems, each with its own latency and failure mode. Because nothing spans them transactionally, correctness comes from idempotent tasks, compensating actions, a fallout queue and jeopardy monitoring.
Allocation is a cost minimisation over shipping, split-parcel cost and delivery promise, evaluated per line rather than per order; the design that survives is one where every line carries its own state, cancellation is a race against the pick face, and a shortfall is a normal outcome with a defined path.