You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From my understanding, when it comes to workflow persisting state and resuming, there would be no difference in the number of hops between Dapr Workflow and Azure Durable Functions since the persistence does not happen in my code but only when my code awaits and gets automatically persisted by the either Dapr Workflow runtime or the Azure Durable Functions Out of Process engine. Then the engine wakes up and calls my code. Am I missing something?
Was not sure where to ask so I asked on both dapr/dapr#7544
The text was updated successfully, but these errors were encountered:
From my understanding, when it comes to workflow persisting state and resuming, there would be no difference in the number of hops between Dapr Workflow and Azure Durable Functions since the persistence does not happen in my code but only when my code awaits and gets automatically persisted by the either Dapr Workflow runtime or the Azure Durable Functions Out of Process engine. Then the engine wakes up and calls my code. Am I missing something?
Was not sure where to ask so I asked on both
dapr/dapr#7544
The text was updated successfully, but these errors were encountered: