How can you ensure the database is the source of truth in the Fluid world?

[thaoula]

Hi All,

I am new to the Fluid Framework so please excuse me if these questions have answered already.

We have an existing multi-tenant application we are working on a Project Management module. The clients have asked us to ensure that they can collaborate on the Project together.

I wanted to explore the use of the Fluid Framework to meet this expectation. However, I am not if it is the right technology.

In a previous question - #9535, I needed a way to generate the containerId on the server so that I can ensure a single container for a Project exists. I am not sure how to solve this at the moment but I wanted to move along and try and solve a different challenge.

When a user navigates to the Project screen, I want to automatically connect them to a Fluid container so that they can start adding/removing/completing Project tasks. This would ensure that other users would be able to see the tasks being added / removed / completed etc.

Any number of users from the same organisation could visit the Project page and make changes. If the source of truth was the fluid container everything would be awesome (like all the demos :) )

However, since this is a real app, we would like the changes made to the Project to be applied to the database and we would like the to ensure the container and the database in sync as much as possible.

So I know we can use valueChanges to detect changes and write changes to the database. But that means the entire project would need to remain living in the container.

So my questions are -

1. Does Fluid make sense for this type use-case?
2. When do you refresh the container? Ie there a changes made outside the container?
3. When do you delete the container, users can come and go anytime?
4. Are there any examples of database driven data being collaborated on using Fluid and then saved back to the database?

Regards,
Tarek