Excellent, thanks... I have a prototype with Event Hubs for accepting Commands, Functions (one per Command) that apply the Commands to an Aggregate Root, then Events routed via Event Grid to Functions - one per Aggregate type, that processes any and all Events that might be raised by that specific Aggregate type. At the moment, one Function per Aggregate type is the only way I can think of to work around cold starts leading to Functions per Event type processing Events out of order for Projections etc. Lots of reading to do - cheers!

Any suggestions for implementing CQRS with Event Sourcing on current Azure feature set? Examples / references? ('CQRS Journey' is a little dated w.r.t newly available Event Grid, etc).

@ Jeremy Likness Traditionally F# templates in Visual Studio have been behind the C# templates, or in some cases, non existent. It's also only recently that F# documentation has been reorganised; previously it has felt like a community effort sponsored by Microsoft, rather than an officially supported language. F# is certainly not promoted as an equal partner to C#. Although it has to be said, F# examples for Azure Functions are quite comprehensive - but there is no Visual Studio 2017 template for them, unlike C# ;-) There's definitely an active user community around F#- it just seems that Microsoft are missing out on an opportunity to promote an alternative to say, Scala.

Do you feel that F# is receiving enough love from Microsoft? Personally I feel it deserves much more support and promotion.

C#, F# (wonderfully productive language), React, React Native, TypeScript, minimal NodeJS through ASP.Net Core JavaScript Services. Learning some R. Not strictly languages, but ES6, Mobx, Graphql (still looking for a solid .Net Core server implementation), HTML5, the usual.