Merge pull request #208544 from hickeys/afr-container-post-recovery

Azure Fluid Relay: Container post recovery considerations.

Author: prmerger-automator[bot]

articles/azure-fluid-relay/how-tos/container-recovery.md

@@ -74,3 +74,11 @@ We aren't recovering (rolling back) existing container. `copyContainer` will giv
 ### New Container is detached
 
  New container is initially in `detached` state. We can continue working with detached container, or immediately attach. After calling `attach` we'll get back unique Container ID, representing newly created instance.
+
+ ## Post-recovery considerations
+
+When it comes to building use cases around post-recovery scenarios, here are couple of considerations on what application might want do to get its remote collaborators all working on the same container again.
+
+If you are modeling your application data solely using fluid containers, the communication “link” is effectively broken when the container is corrupted. Similar real-world example may be video-call where the original author has shared the link with participants and that link is not working any more. With that perspective in mind, one option is to limit recovery permissions to original author and let them share new container link in the same way they shared original link, after recovering the copy of the original container.
+
+Alternatively, if you are using fluid framework for transient data only, you can always use your own source-of-truth data and supporting services to manage more autonomous recovery workflows. For example, multiple clients may kick off the recovery process until your app has a first recovered copy. Your app can then notify all participating clients to transition to a new container. This can be useful as any currently active client can unblock the participating group to proceed with collaboration. One consideration here is the incurred costs of redundancy.