Skip to content

.Net: Process Framework State Persistence, Checkpointing and Fail-over #11959

Open
@ddobric

Description

@ddobric

Ho all,

1 State Persistence

What is the current strategy for state persistence of the process framework across different scenarios?
I guess, if using Orleans, the state is saved to the grain (actor) and persisted by Orleans?
What is the strategy for all other scenarios like local run, DAPR etc.

2 Checkpointing

What is the current strategy for chrekpointing of the framework? For example, step 3 fails after 2 days of execution. The application is restarted, and what happens next? The expectation is that the application continues where it is stopped.

3 Fail-over

What is the concept of the framework when we run the application with the same process on two nodes = Fail-Over scenario? The same was solved by the Service Bus Session concept and Durable Functions. It is an important enterprise scenario.

All 3 mentioned scenarios are extremely important in enterprise applications.

Metadata

Metadata

Assignees

Labels

.NETIssue or Pull requests regarding .NET codeprocesses

Type

No type

Projects

Status

Backlog: Planned

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions