Skip to main content
bus-serial enforces one active event per bus, while different buses can process events simultaneously. Companion runnable example:

Lifecycle impact

  1. Events enqueue per bus in FIFO order.
  2. Each bus holds its own event lock.
  3. A busy bus does not block other buses.
  4. Queue-jump child events can preempt that same bus queue when awaited in-handler.

Execution order example

Notes

  • This is typically the best default for multi-bus systems.
  • It preserves local determinism while retaining cross-bus throughput.