disruptor marshalling

167 views
Skip to first unread message

Francesco Nigro

unread,
Sep 2, 2014, 7:07:23 PM9/2/14
to mechanica...@googlegroups.com
Hi,
I'm realizing a simple Cqrs app (in term of architecture..not philosophically :)) and i'm wondering if for the command handling part is correct to marshall (into Bson, 'cause i've choosen mongoDb as write and read datastore) the write models in the same thread of the command execution..The unmarshalling into commands (using https://code.google.com/p/fast-serialization/) is handled in the same thread too in order to allow the escape analysis to turn the business commands and produced entities into stack allocated objects..is a good way of think?For the sake of completeness , prior to the unmarshall-command execution-marshall, the messages are consumed by a java-chronicle based journalizer while the marshalled entities are published to a second ringbuffer with only a mongodb sender consumer...

Michael Barker

unread,
Sep 3, 2014, 3:15:37 AM9/3/14
to mechanica...@googlegroups.com
I've answered this question on the Disruptor list.

Mike.


On 3 September 2014 00:07, Francesco Nigro <nigr...@gmail.com> wrote:
Hi,
I'm realizing a simple Cqrs app (in term of architecture..not philosophically :)) and i'm wondering if for the command handling part is correct to marshall (into Bson, 'cause i've choosen mongoDb as write and read datastore) the write models in the same thread of the command execution..The unmarshalling into commands (using https://code.google.com/p/fast-serialization/) is handled in the same thread too in order to allow the escape analysis to turn the business commands and produced entities into stack allocated objects..is a good way of think?For the sake of completeness , prior to the unmarshall-command execution-marshall, the messages are consumed by a java-chronicle based journalizer while the marshalled entities are published to a second ringbuffer with only a mongodb sender consumer...

--
You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mechanical-symp...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Francesco Nigro

unread,
Sep 3, 2014, 4:00:33 AM9/3/14
to mechanica...@googlegroups.com
Thnks Mike!
To unsubscribe from this group and stop receiving emails from it, send an email to mechanical-sympathy+unsub...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages