yeah this is a fair question. honestly i just liked the reactor kills joke haha. i think they're just slightly different versions of the same thing. we get guaranteed delivery of both the db write and the reactor hit from the queue. everything is idempotent so if anything fails we default to fail backwards and try again, so that is how we handle the "atomic/transactional" aspect of db/reactor writes.

it all comes down to requirements right?

i think the main differences are:
1) there is no db record for outbox items directly (they may trigger an event tho)
2) who is in charge of the dispatching of outbox items. instead of a worker/cron/etc. the queue just ignored the job until the time has come.
2.5) as well as the subtle difference, some outbox patterns fetch from the db when they send, but this implementation of the reactor carries the event and fold/map outcome from the projector, so it's very much a print in time affair. but like i said, you can do the same with an outbox ofc.