EventsSourcing-on-Azure-Functions
EventsSourcing-on-Azure-Functions copied to clipboard
A library to demonstrate doing Event Sourcing as a data persistence mechanism for Azure Functions
Need to have a **Command** class which can be bound to a parameter on an Azure function with _autoresolve_ properties for command name and unique identifier. If the unique identifier...
The bank account example is a nice (and cliché) example of event sourcing but it would be good to have a larger multiple-domains example too to show intra-domain messaging and...
See https://github.com/CraftyFella/AzureStorageLocal
In the "bank account" example add a cross account transfer to show how the transaction itself can be backed by an event stream and that can be acted on as...
The `EventSourcingOnAzureFunctions.Common.csproj` project should automatically build and be pushed to NuGet.org
A version of the **EventGridEcho** function that sends the message out via SignalR so that we can have a "What's happening" ticker in the CloudBank Blazor UI.. See : https://devblogs.microsoft.com/aspnet/azure-signalr-service-now-supports-event-grid/
https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview
See https://docs.microsoft.com/en-us/azure/azure-functions/functions-dotnet-dependency-injection#customizing-configuration-sources The configuration of the different **maps** (Event Maps, Projection Maps and Classification Maps) should be changed to use the new IFunctionsConfigurationBuilder way of injecting config.
An intriguing side effect of the "a command or query instance is an entity with its own backing event stream" combined with "notifications are sent when an event is appended...
To prevent having to run **projections** and **classifiers** from the beginning every time it should be possible to take "snapshots" as at a given sequence number and use these to...