When the bus stops

The event-driven side decouples writes from reads. That holds even when the parts in between fail. Stop the broker or the consumer, keep writing, and watch the source of truth and the projection drift apart, then meet again.

1. A person of your own

Seed people are shared and read-only, so make one to change.

2. Break something

Only for you. Each switch turns itself off after 3 minutes.

The relay cannot publish: events wait in the outbox table, next to the data they describe.
Events are published but nobody applies them: they wait on the queue and are redelivered.

3. Keep writing

Writes go to the HR and Employment services, which do not care whether the bus is up.

Source of truth vs projection

Owners (HR and Employment events services)
Projection (query service)
Console

  
Nothing was lost: the outbox kept every event in the same transaction as the write, and the queue kept every published event until the consumer applied it. Reads kept working throughout; they were just older. That is the event-driven bargain: availability now, consistency eventually. Federation has no bus to stop, but its reads stop with the owning service.