Comments on: Messaging Semantics: Ownership

By: Steven Roberts

Steven Roberts — Sun, 31 Mar 2013 13:50:00 +0000

Jimmy, as Andy asks I would also like to know about message placement. I asked on the NServiceBus user group but no response there. I’m guessing each service needs a separate assembly to enable sharing? I’d appreciate your thoughts, or if more complex than can be answered here, how about a post?

By: andy

andy — Fri, 21 Dec 2012 21:56:00 +0000

Would have been nice with post on where to put the message DTO definitions. Shared common message assembly? or copy the message definitions into both the publisher and the subscribers sourcecode?

By: The Morning Brew - Chris Alcock » The Morning Brew #1259

The Morning Brew - Chris Alcock » The Morning Brew #1259 — Fri, 21 Dec 2012 09:39:18 +0000

[...] Messaging Semantics: Ownership – Jimmy Bogard resumes his series on Messaging Semantics, with a look at the role that message ownership should play in the meaning of your messages, commands and events [...]

By: Distributed Weekly 186 — Scott Banwart's Blog

Distributed Weekly 186 — Scott Banwart's Blog — Fri, 21 Dec 2012 09:05:54 +0000

[...] Messaging Semantics: Ownership [...]

By: Lev Gorodinski

Lev Gorodinski — Fri, 21 Dec 2012 00:02:00 +0000

To add to his, I think commands/replies/events are great artifacts for defining the API of a system in a top-down fashion. They can be incorporated directly into use cases as well as referenced in DDD context map diagrams.