A Fluid container can be attached or detached. An attached container is connected to a Fluid service and can be loaded by other clients. Also see Detached .
If your app is bundled separately from your container code, Fluid can use a code loader to download and load the container code bundle dynamically.
The container is your application’s entry point to the Fluid Framework. It runs your container code and is the object through which you’ll retrieve your shared objects.
You’ll write container code to define which shared objects your scenario uses and how you’ll access them.
Data Objects are higher-level shared objects, compared to distributed data structures, which are low-level shared objects. Data Objects are used to organize distributed data structures into semantically meaningful groupings for your scenario, as well as providing an API surface to your data.
A Fluid container can be attached or detached. A detached container is not connected to a Fluid service and cannot be loaded by other clients. Newly created containers begin in a detached state, which allows developers to add initial data if needed before attaching the container. Also see Attached .
Distributed data structures (DDSes)
DDSes are the data structures Fluid Framework provides for storing collaborative data. As collaborators modify the data, the changes will be reflected to all other collaborators.
Responsible for connecting to a Fluid service and loading a Fluid container.
A service endpoint that is responsible for receiving, processing, storing, and broadcasting operations.
Fluid service driver
Client code responsible for connecting to the Fluid service.
A distributed data structure (DDS) or Data Object.
Fluid’s API surface makes use of URLs, for example in the
resolve() method and
method. The URL resolver is used to interpret these URLs for use with the Fluid service.