Events: Fat or Thin?

Re:Events: Fat or Thin? by nfgivivu on Sunday October 30, 2022 @09:16AM (#33394233)

I'd settle for developers just making sure events were events that have happened and not action commands they want to happen.

Nothing is worse than an event driven system polluted with action commands.

[ Parent | on HN ]

Re:Events: Fat or Thin? by mrkeen on Sunday October 30, 2022 @09:48AM (#33394478)

I agree in principle, but I also to need action commands when crossing boundaries in and out of the event system (e.g. to the user, or to an external provider.) Of course I still phrase them in the past tense:

    PurchaseRequested { userId = ... }

    PaymentRequestSentToStripe { userId = ... }

It really helps with debugging, especially if the user gets into some failed state (and the events tell you that they accidentally requested twice)

[ Parent | on HN ]