How should address changes be coordinated with related entities such as orders or shipments?

How should address changes be coordinated with related entities such as orders or shipments?

• A. Do nothing
• B. Emit events on changes; update dependent records or trigger downstream workflows; maintain integrity through foreign keys
• C. Maintain integrity through foreign keys only
• D. Disable changes

Answer: (B)

Coordinating address changes across related entities hinges on emitting events when changes occur and propagating those updates to dependent records or downstream workflows, while keeping data integrity with foreign keys. When an address updates, emitting an event lets orders, shipments, billing, and notifications react appropriately—updating the order’s address, adjusting shipment labels and delivery instructions, potentially recalculating taxes or shipping options, and triggering customer notifications. This event-driven approach keeps systems decoupled and scalable, while the foreign key constraints ensure referential integrity so relationships between customers, addresses, orders, and shipments remain valid. Doing nothing would leave data and processes out of sync, and relying only on foreign keys wouldn’t trigger the necessary downstream actions or workflows. Disabling changes also blocks legitimate updates, breaking the system’s ability to stay current.