Honestly, I just assumed it was someone using Azure's basic services without being ready for a massive traffic spike. I was a bit miffed but understanding. But Microsoft not being able to scale on their own cloud service seems like a massive failure.
> Fluid does not use Operational Transforms, but we learned a tremendous amount from the literature on OT. While OT uses operations that can be applied out of order by transforming operations to account for recent changes, Fluid relies on a Total Order Broadcast to guarantee that all operations are applied in a specific order.
> Does Fluid use CRDT?
> Fluid does not use Conflict-Free Replicated Data Types (CRDTs), but our model is more similar to CRDT than OT. The Fluid Framework relies on update-based operations that are ordered using our Total Order Broadcast to prevent conflicts. This allows us to have non-commutative operations because their is an explicit ordering.
Their model sounds a lot like how Croquet (https://en.wikipedia.org/wiki/Croquet_Project) used to work, where every operation is given a globally-ordered timestamp as it passes through a shared message router.
Looks like a CRDT/Operational Transform server/pubsub as a service. There are also some open source frameworks on GitHub which doesn't depend on Azure.
Adding more context: Fluid uses a mix of CRDT + OT to maintain state across multiple clients. I wrote a quick high level explanation of how Fluid uses eventual consistency and why it matters for real time collaboration: https://matt.aimonetti.net/posts/2020-09-solving-real-time-c...
> With Fluid Framework, developers can easily add multi-user interactivity to their apps — powered by the same code that drives collaboration in Microsoft 365 experiences for millions of users.
edit: there is web archive version:
https://web.archive.org/web/20200909053211/https://fluidfram...