The TradesLoader component can be refactored to do its job of loading the Trades from a file. In order to complete its task, the TradesLoader will publish the Trades to a data-holding structure like a bucket. In Messaging terms, this is called a destination or a channel. The rest of the components should be picking up the Trades from this channel, which acts as a conduit.

Note that we did not introduce a full-blown enterprise messaging solution here. It would be overkill, because it would introduce a whole stack of infrastructure and open doors to different programming models.

See Figure 1-2, which depicts a sort of parallel process using a standalone messaging model.