Problem
Paradox Shop's order service below writes the new order straight to PostgreSQL and separately publishes an order-created event directly to a message queue. Sometimes the commit succeeds but the publish call fails or the process crashes in between; the order exists, but nothing downstream ever hears about it. Fix the pipeline to eliminate this dual-write gap: a committed order should always, and only, produce its event.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.