[drewcoo]

Thank you. Came here to say that.

When I've seen this fat event pattern it's been because different services' responsibilities were not fully separated. And that's tight coupling. Fat events imply tight coupling.

The "thin" pattern described in the article goes like this:

1) service FOO gets an event

2) FOO then has to query BAR (and maybe BAZ and QUUX) to determine the overall state of everything to determine what to do next

And #2 means all of that is kind of "thin" is tightly coupled, too.

I've also personally seen thin events that are not the article's thin strawman.

I sometimes wonder if people understand coupling or design.