Duncan Jones

Or maybe Azurite? https://github.com/Azure/Azurite

Would need to use a common time frame - and I think there is a minimum sensible granularity to be found too (maybe 1 second?)

**Thoughts** It would be possible to insert retrospective events which means that any cached or snapshotted state impacted would need to be recalculated. _It would be preferable if this did...

Will use the same type of attribute as for event streams but with a different attribute name to differentiate e.g. : ``[TimeStream("Bank","Account", "A123456")]``

If SignalR hub set incorrectly we need to ignore rather than throw a `System.Net.Sockets.SocketException` ? ( No such host is known )

Additional reference for hooking up the front end: https://lgulliver.github.io/serverless-chat-with-blazor-webassembly/

Linked to issue #12

This could be really difficult because of this:- https://docs.microsoft.com/en-us/azure/azure-functions/durable-functions-checkpointing-and-replay#orchestrator-code-constraints

This means all asynch interaction with the **Command** event stream must be performed inside of an Activity type of function

In fact there needs to be some more work as when the durable function orchestration is called again (as it is for the orchestration function to work) then a new...