Look at removing the custom projections

[StuartFerguson]

Currently a number of services have projections that build up a specific stream for them to listen on with a persistent subscription.

This has 3 downsides.

• More strain on the ES building up these streams
• An extra point of failure if the projection fails
• More data being written to the ES (albeit they are link to's)

The right way of handling this would be all events are sent to the subscriber and it decides what to handle/not handle and silently handle event its not interested in.

I think there is benefit in having 2 projections
EstateAggregator - Build a single stream for all the estate events (useful for rebuilding whole read model and probably the stream to use for the main read model processing)
MerchantAggregator - Build a stream per merchant with all merchant events

The call back stuff needs to be reviewed seperately so leave that for now

[StuartFerguson]

Had a look at this not worth the effort for the little gain provided