Documentation Needed -- Guidance for Business Continuity and Disaster Recovery for Dapr Workflows

Aperta
  • Qualcosa non va?
#4,683 1 commento 2 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Ambito
backend, cloud, documentation

Direzione di ricerca

L’issue non nomina file né test. Inizia esaminando la documentazione esistente di Dapr sulla resilienza e le guide sui workflow, quindi definisci l’ambito della panoramica BCDR concentrandoti sullo stato del workflow, sullo stato dell’applicazione, sul failover, sulla progettazione dei workflow e sul ripristino dello state store. Il lavoro è completato quando una guida di Dapr Docs revisionata e facilmente reperibile copre questi scenari.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Describe the feature

This was extracted from Issue 8590 on 3/23/25.

Essentially resurrecting crashed workflows manually is just one possible activity in a disaster recovery scenario involving Dapr Workflows.

A disaster is when something causes a system and/or its state stores to stop working and become inoperable. The remedy for this is conducting some sort of disaster recovery activities, including failover (maybe automatically) to another geographic location or systems.

It would be most helpful to have some Dapr Docs guidelines for BCDR, aka Business Continuity and Disaster Recovery:

Specifically, scenarios for Dapr Workflow Disaster Recovery, an overview of approaches including the following topics:
o Approaches for Failover of Workflow State, Failover of Application State, and other high level concepts.

o Designing Dapr Workflows so as to enable speedy Disaster Recovery. Things to do, and not to do.

o How to edit the Workflow State Store to enable Disaster Recovery.

Finally, note that there currently exists a number of documents and videos concerning how to use Dapr's resiliency related features. Resiliency Features act to help prevent crashes and Dapr's resiliency features are very rich and well tested.

But, sometimes things happen that overwhelm or neutralize even the best Resiliency Features. Like data center outages and communications outages that prevent failover to other data centers. Such outages are typically caused by weather emergencies or human error. Take a look at the outage logs of Azure or AWS or Google to see how common major outages are. These are the situations in which robust designs and good documentation (as outlined above) have the potential to significantly reduce the time it takes to recover the system(s) and get it back in operation. And that is the basic intent of this issue plus the related Disaster Recovery topics above.

Googling "Dapr Disaster Recovery" currently yields few, if no, useful results specifically concerning Dapr. It would be great if an overview article in Dapr Docs named something like "Business Continuity and Disaster Recovery for Dapr" were to show up at the top of this search.

Release Note

RELEASE NOTE:

Lingua principale
SCSS
Stelle
1k
Fork
808
Merge medio
2g 15h
PR unite (30g)
73

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dapr/docs

Tutte le issue di dapr/docs

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.