Hello Abdul Rahman,
**Thank you for submitting your question on Microsoft Q&A.
**
The main point is clear: the Fluid Relay service functions as a relay, not a database. It’s designed for low latency and is stateless, allowing real-time collaboration by synchronizing changes across clients. The shared state resides on the clients themselves, rather than in a server-side storage that you can access with a simple HTTP request. Managing the containerId
and using the Fluid client libraries to reconnect and rebuild the shared state is handled by your application.