views:

17

answers:

0

Requirement

I'm using PRISM for developing a financial application. Our requirement is to be able to communicate across modules/process/machine boundaries.

For our first delivery we only want to be able to communicate between modules. However, we want to build a design which can be extended to cross-process/machine at a later stage without much change to existing stuff.

Solution im considering

I'm considering using EventAggregator for the first delivery. I plan to extend it at a later stage by building a listener module that can listen to the events and wire them to a bus for cross process communication. I'm concerned about two things here :

  • Is it as elegant as i think it is. In terms of simplicity and providing the flexibility to extend it later using any sort of listener and wiring we want.
  • When the volume of communication increases, would it hit the performance significantly.