Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Accidental decoupling is where you have a complex state machine encapsulating a business procedure with multiple steps, and it's coordinated as messages between and actions in multiple services.

That might need emphasis on "in multiple services."

Within the same service, a granular set of messages (events) can still be useful for auditing or creating good read-model "projections" of what happened.



I thought event sourcing as a data storage strategy and queues as an execution model were orthogonal concepts?


It's true that the messages (state machine transitions) don't have to be a durable source of truth, but there are similar arguments to be made for granularity.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: