Use Projection Model from JasperFx.Events

[jeremydmiller]

This is very heavily in flux

This is me keeping notes on incremental changes that need to happen before switching to the projection support in JasperFx.

Marten Refactoring

• IAggregateProjection.ConfigureAggregateMapping() needs to get moved to some kind of Marten specific marker interface
• Move CacheLimitPerTenant to AsyncOptions
• IAggregateProjection should expose ShardName
• Abstract AsyncOptions a bit by keeping a model of what should be torn down. Instead of tracking IDocumentOperations, track tables and document collections
• For the love of everything holy in this world, get the logic for finding the aggregate identifier into something in JasperFx itself and reuse that logic everywhere from now on to dodge more of the endless strong typed identifier permutation hell

[jeremydmiller]

Tasks

Some of this crosses into JasperFx.Events as well, but it's easier to tracking everything here.

• Implement IEventStorage on DocumentStore
• Build Marten version of IProjectionStorage that encapsulates an IDocumentStorage and session
• SingleStreamProjection inherits from JasperFxSingleStreamProjectionBase
• MultiStreamProjection inherits from JasperFxMultiStreamProjectionBase
• EventProjection inherits from JasperFxEventProjectionBase
• Do something about FlatTableProjection
• Have Marten IProjection implement JasperFx interfaces
• AsyncDaemon implements JasperFx interfaces
• EventGraph.ProcessEventsAsync() should use IInlineProjection
• Implement IStorageOperations on DocumentSessionBase
• Basically redo the projection validation
• Do something to create a new interface for projections that need to modify the DocumentMapping in Marten
• EventGraph inherits or uses IEventRegistry/EventRegistry
• Test the dotnet run -- projections command