FubuTransportation Spike

[Corey Kaylor]

I have been discussing ideas for a while with others on using Fubu with messaging systems. I have pushed a public repo proof of concept that is working with Rhino.ServiceBus, in theory it will work with any of the other bus implementations available if they have similar hooks to tie into. This will essentially bring all the convention, behaviors, bottle awesomeness to messaging. With a little effort I'm fairly confident that you could tie in diagnostics, potentially an admin UI exposed through OWIN / Kayak.

https://github.com/CoreyKaylor/fubutransportation-spike

Would be interested in others constructive thoughts.

[jmarnold]

Just to clarify for everyone:

The idea is that message handling deserves our conventional russian
doll approach, right? By that I mean that given Message X, this spike
enables X to be processed through a behavior chain vs. the typical
IMessageHandler<T> approach?

[Corey Kaylor]

Yeah, sorry for jumping to the punchline without the back story. That's kind of how I roll if you haven't noticed.

Bottles, Behaviors, nested container to handle lifecycle of the various message handler dependencies, conventions that drive how messages are consumed.

The sample demonstrates what a saga might look like in a conventional approach.

--
You received this message because you are subscribed to the Google Groups "FubuMVC Development Group" group.
To post to this group, send email to fubumv...@googlegroups.com.
To unsubscribe from this group, send email to fubumvc-deve...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fubumvc-devel?hl=en.

[John Simons]

Hi Corey,

Any spike of this concept against NServiceBus v2 ? Or any tips on how to go about it?

Also,

A bit confused on how to conventionalise(if there is such a word) things like "Send" to a specific endpoint.

Cheers

John

---

From: Corey Kaylor <co...@kaylors.net>
To: fubumv...@googlegroups.com
Sent: Sunday, 12 February 2012 7:39 PM
Subject: Re: [fubumvc] Re: FubuTransportation Spike

[Corey Kaylor]

I know NServiceBus has the concept of an IMessageModule, but I'm not sure if it provides the hooks necessary to "handle" a message. I'm not familiar enough with NServiceBus to say for sure.

One possible way with NServiceBus is to have an implementation of IMessageHandler<object> that would handle all messages, and this could be the hook to invoke the behavior chain.

Send conventions have its limitations or at least the ones I've thought through. One of the most basic things that could be setup, is that when a method has output, there would be a behavior after the ActionCall that issues a bus.Reply, and potentially based on other conventions, it could issue Publish, etc. Feel free to elaborate if you have more specific ideas in mind that you would like to be driven by convention.

[ahjohannessen]

I think this is awesome and opens up for some very interesting scenarios :) Gonna show my coworkers this tomorrow :)

[Joseph Vano]

On my inputs, I put an interface, something like "ICauseNotification", and have a behavior that is added after the ActionCall to send a message via NServiceBus for those input types

There is class in the middle that builds the message "IMessageBuilder<T>" from the input.

-

Joey