We built Fluid to make it simpler for developers to build real-time collaborative experiences using Web technology.
Fluid enables distributed, collaborative applications by providing developers with eventually consistent distributed data structures, a flexible component and app model, and a reference server implementation called Routerlicious.
Teams are using Fluid for low latency collaboration, zero setup data persistance, and on-by-default cross app compatibility. Among other projects, our partner teams are building components for text editing, gaming, command line tooling, and IoT.
Fluid's distributed data structures make it easy to write apps that are collaborative just like you would build single-user applications and experiences. Fluid handles keeping your data in sync across multiple clients, so you can focus on your app's business logic. Fluid's data synchronization is fast, efficient, and requires very little bandwidth. Fluid is extensible, too. You can write components which can be re-used or you can even create new distributed data structures.
Get up and running quickly using our documentation at https://aka.ms/fluid.
| Project | Status |
|---|---|
| Packages | |
| Routerlicious | |
| Admin | |
| Auspkn | |
| Historian | |
| Historian Chart | |
| Cobalt | |
| GitSSH | |
| GitRest | |
| Headless Chrome | |
| Fluid metrics | |
| Fluid metrics chart |
To ensure minimal latency and smoother user experience, we deploy our backend in a few different Azure regions. If you are closer to west coast, use the following endpoints located at Washington:
Our code is deployed immediately after check in to:
East coast developers are encouraged to use the following endpoints(located at Virginia):
Developers in Europe can use the following endpoints (Located at Netherlands):
