FluidFramework

Has anyone tried Microsoft's fluid framework for collaborative editing? https://github.com/microsoft/FluidFramework https://fluidframework.com/

Have you seen FluidFramework? It's open source (MIT): https://github.com/microsoft/FluidFramework I think the first product they're building on it is Loop: https://www.zdnet.com/article/microsoft-introduces-loop-a-ne...

And the content-adressable filesystem that it uses is git [1]. It uses git with a javascript implementation of it [2] or node bindings to a c one [3]. 1. https://github.com/microsoft/FluidFramework/tree/main/server... 2. https://github.com/isomorphic-git/isomorphic-git 3. https://github.com/nodegit/nodegit

The Office 365 backend uses git to store snapshots of documents. [1] https://github.com/microsoft/FluidFramework/tree/main/server...

Full disclosure I work at MSFT and on the fluid framework. If you are interested in this you may also be interested in the fluid framework, https://github.com/microsoft/FluidFramework We use websockets and solve a lot of the state management problem called out here by keeping very little state on the server itself. The primary thing on server is a monotonically increasing integer we use to stamp messages, this gives us total order broadcast which we then build upon: https://en.m.wikipedia.org/wiki/Atomic_broadcast Here are some code pointers if you want to take a look: The map package is a decent place to look for how we leverage total order broadcast to keep clients in sync in our distributed data structures: https://github.com/microsoft/FluidFramework/blob/main/packag... The deltamanger in the container-loader package is where we mana

(Disclosure: Work at Microsoft, but I work in Azure and some open source stuff, not on or directly with Fluid/Office/etc.) That's just a trademark clause for Microsoft logos and brands. The Fluid Framework itself is MIT licensed [0] and doesn't require exposing any of those logos/brands when you use it, so the framework itself is fairly open for usage. I think the main thing that would slow down adoption for Fluid is that the only "production" backend is an Azure service, which isn't part of the open source Fluid Framework. Other open source backends[1] aren't recommended for productions. Until there are some open source ones, I'd assume adoption will be limited to folks in the Azure ecosystem. [0]: https://github.com/microsoft/FluidFramework/blob/main/LICENS... [1]: https://fluidframework.com/docs/deployment/service-options/

Has anyone tried to develop anything with MSFT's Fluid Framework [1], which is used to build Loop? I have not got a chance to check details. But it seems quite nice. Any general remarks are welcome. Particularly, I'm interested in understanding customizability of Fluid components, integration with React, and any concerns about Azure service lock-in. [1] "The Fluid Framework is a library for building distributed, real-time collaborative web applications using JavaScript or TypeScript." https://github.com/microsoft/FluidFramework

Which looks like Quip, which looks like OneNote, which looks like a million other note-taking apps before it. I think the more interesting aspect is the extreme coauthoring; it looks like the underlying tech is open source as well which is pretty interesting for a lot of applications: https://github.com/microsoft/FluidFramework

You could start by watching the Fluid Framework github.com/microsoft/fluidframework (I'm a dev on the team). We solve a lot of these problems. This whole article speaks to the longer term vision. Even the article's Title is effectively our internal pitch: a web first database... that enables very low latency collab

Disclosure: I work on a related project (Fluid Framework) that makes application agnostic CRDTs easily available. The CKEditor folks did a great job building an OSS text editor and they did an especially strong work building a text editor that works well with collaboration. I've made a few OSS rich text editors work (mostly) with Fluid [0, 1] and the design of the text editor really changes how easily collaboration can be added. Luckily the text editor accepts remote changes, integrating an OT or CRDT solution is approximately the same. They also did a great job explaining the problem. My experience has been that people don't intuitively understand why real time collaboration is a tricky problem. I didn't. First of all, for a bunch of use cases websockets + redis + a last write wins conflict resolution (or some similar solution) is totall

One would think that Microsoft, if any, would be able to handle a traffic spike... And to block a marketing site from more traffic feels like a complete fail. There's some info on the Github: https://github.com/microsoft/FluidFramework Still doesn't say how it "works", like, do we need servers? How is it distributed? Is there a database-layer?..