Sergey Bykov

Per @shlomiw: >The problem is that I can have 100k's, or millions of non active players, and only 1000s active. Is the proposed pattern here to invoke millions of grains...

@shlomiw >I'd still need to activate 100k's of grains which can be heavy on Orleans, but I can do it gradually in a moderated way. That's related to my question...

@SebastianStehle Your scenario does sound different if you only need to look up a specific grain. It's an interesting question if such a scenario warrants a general purpose feature (`IsActivated(grain)`)...

@shlomiw Is there a way to indicate to the grains that they need to perform an update and what exactly they need to do (e.g. by writing the update command/expression...

No worries. 😊 >I have to update their score and it affects the leaderboards (we query the leaderboards data directly from the DB). Can you apply the change to storage...

>What about [OnlyIfActivated]? - I do find it useful in some scenarios, i.e. update specific grain's cached state if alive, or monitoring a grain. What should happen with calls to...

@SebastianStehle What is your opinion here? Would that work for your case or you need to get a response back from the rule engine grain in this scenario?

Wouldn't the simplest and least invasive change here be to expose a way to ask if the target grain is currently activated? That way we wouldn't need to introduce attributes,...

This should be much easier to do in 3.0.0 with us using the Bedrock layer of ASP.NET Core.

@ReubenBond has been working on that. He can explain better.