TrackSSA0056

Commit Succeeded, Publish Failed

Hard

Problem

Paradox Shop's order service needs to write each new order to PostgreSQL and publish an order-created event to a message queue, but those are two separate systems with no shared transaction: if done as two independent calls, a commit can succeed while the publish call fails or the process crashes in between, leaving an order that exists but that nothing downstream ever hears about. Design a pipeline from scratch that eliminates this dual-write gap: a committed order always, and only, produces 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.

Drag components from the library onto the canvas, then drag from a component's right handle to connect it to another.

100%

Design canvas

Sign up to start designing

Sign up free

Premium is free for 58 more days.