Rabbinatix
Sign inGet started
Store

Event-driven order pipeline

FreeSystem map
@rabbinatix/event-driven-architecture by Rabbinatixupdated Oct 13, 2026

An orders service publishes events; separate workers update stock and send emails, each at its own pace.

6 systems and 5 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.

As the map's Connections view shows it: traffic flows from the system that calls to the system it calls.

7 connections · 5 APIs

  • Orders Service → Event Bus
    • POST/topics/order-events/publishPublish an order event
  • Inventory Worker → Event Bus
    • GET/subscriptions/{name}/pullTake the next events
  • Notification Worker → Event Bus
    • GET/subscriptions/{name}/pullTake the next events
  • Inventory Worker → Orders Service
    • GET/api/v1/orders/{id}One order
  • Notification Worker → Orders Service
    • GET/api/v1/orders/{id}One order
  • Inventory Worker → Inventory Service
    • POST/api/v1/reservationsReserve stock for an order
  • Notification Worker → Email API
    • POST/v3/mail/sendEmail the customer

Systems (6)

Orders Service
Takes orders and publishes what happened.
Event Bus
Carries events to whoever subscribed.
Inventory Worker
Reserves stock when an order comes in.
Notification Worker
Emails the customer about their order.
Inventory Service
How many of each product are left.
Email API
Sends email.

A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.

Versions