Reuben Bond

@KSlingerland are you able to use Keyed DI for TimeProvider at the application level?

@koenbeuk is there anything remaining here or is this ready for review? Apologies for the delay

(rebased on main)

@koenbeuk thank you for great work on this PR and for your patience. I have pushed some updates to implement the identification strategy we discussed (using sender's `GrainId` + `MessageId`)....

I need to spend some more time with the current ADO.NET bits. Ideally, I would like to see how we can simplify it. Perhaps all DBs can use asynchronous IO...

Apologies, @Arshia001 - I'm following along with interest (and I briefly mentioned this thread in [Gitter here](https://gitter.im/dotnet/orleans?at=5d655ae3c8228962acd3ef1c)). I'm still not entirely sure what the most idiomatic F# model would be....

`let sayHelloProxy = i.GrainFactory.proxyi HelloWorkerGrain.sayHello (i.Identity.key + 42L)` What does the `+ 42L` do there?

Ok, I think I understand now. The grain calls into another grain (its key + 42) to say hello periodically. The syntax seems alright. I think it matters more what...

Good idea

Is your test scenario code on github?