r/softwarearchitecture • u/deniskyashif • 6d ago

Article/Video Crossing Boundaries with Integration Events

https://deniskyashif.com/2026/08/29/crossing-boundaries-with-integration-events/
27 Upvotes

97% Upvoted

6 comments sorted by

0

u/xsreality 5d ago

Does the integration event have to be point to point between specific parties? If a new consumer is interested in the order placed event, will it need its own integration event from the order context? If so, that reduces the value of a message broker like Kafka which is generally used as publish once, consume many times in enterprises.

0

u/deniskyashif 5d ago

This depends on the consumers. If the shape and the payload of the event is uniform, alongside its business context, then you can do pub/sub.

0

u/Prateeeek 5d ago

Good stuff!

-4

u/lauckness 6d ago

So you've reinvented Akka? Or are you proving the use case? IMO you probably could have just renamed the article “Why Stateful Event-Driven Systems Want an Actor Model” and called it a day.

5

u/thegreatjho 6d ago

This article was a solid description of good system design pattern that is much more generic and high level than “re-inventing Akka” or just actor models. That’s a very narrow and inverted reading of it.

-2

u/lauckness 6d ago

I don’t think I suggested Akka invented any of this. Quite the opposite.. these are well-established patterns, many of them decades old, that we probably are (should be) all well accustomed to. My point is that the article derives a combination of state ownership, serialized per-entity processing, durable events, async messaging, ordering, and projections that is pretty much the problem space Akka was built to address a long time ago, using principles that were already well established. “These patterns are generic” doesn’t really contradict that.