3 ms·
This has nothing to do with event sourcing. What you're describing is event-driven integration. Rarely the events used to source the domain model should be the
by dm3 8y ago
This has nothing to do with event sourcing. What you're describing is event-driven integration. Rarely the events used to source the domain model should be the same as the ones used for the messaging integration. Unfortunately, due to the repetition of the term "event" the purpose gets confused most of the time. The "Data on the Outside versus Data on the Inside"[0] paper makes a good distinction even though it doesn't use the same terms.
[0]: http://cidrdb.org/cidr2005/papers/P12.pdf http://cidrdb.org/cidr2005/papers/P12.pdf
- nicodjimenez 8y agoThis is a good point (about how messaging integration requests differ). I think the choice comes down to whether at least once or exactly once makes more sense for a specific unit of shared data / functionality. For exactly once, APIs and RabbitMQ shine for connecting services. I’m still wrapping my head around when to do what in SOA. Thanks for the link btw.
- nicodjimenez 8y agoBtw why is it bad to use same events for messaging / data integration?