Case: each octogotchii (is that the correct pluralization? :-) ) needs to have a state (age/activity counter) stored in our own backend.
Guess we can start with an Azure Function that stores this in TableStorage? Or can we leverage the state store for a Durable Function and rehydrate that state on each incoming HttpPost ?
Stuff we need to store:
octogotchi name (personalize it through a workflow secret?)
Case: each octogotchii (is that the correct pluralization? :-) ) needs to have a state (age/activity counter) stored in our own backend. Guess we can start with an Azure Function that stores this in TableStorage? Or can we leverage the state store for a Durable Function and rehydrate that state on each incoming
HttpPost
?Stuff we need to store: