[Thoughts] Projections and Classifiers on queue based processor

[MerrionComputing]

If projection and classifier requests are "enqueued" it would be possible for the receiving end to prevent running the same projection/classifier twice by basically tagging any subsequent requests on as a "listener" to receive the answer along with the first caller when the projection or classifier completes.

This should allow performance improvements and cost reduction without the complexity of a proper cacheing strategy.

[MerrionComputing]

Currently failing with

Cannot bind parameter 'writeContext' to type IWriteContext.
Make sure the parameter Type is supported by the binding.
If you're using binding extensions (e.g. Azure Storage, ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. builder.AddAzureStorage(), builder.AddServiceBus(), builder.AddTimers(), etc.).