crdt-woot
FluidFramework
Our great sponsors
crdt-woot | FluidFramework | |
---|---|---|
2 | 12 | |
16 | 4,613 | |
- | 0.4% | |
0.0 | 10.0 | |
about 2 years ago | 3 days ago | |
TypeScript | TypeScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
crdt-woot
-
Collaborative Editing Using CRDT WOOT
Hi, I would like to share this collaborative editor I have created using the CRDT WOOT algorithm as described in the paper Data Consistency for P2P Collaborative Editing. You can try it here. (I added some visualisation of what happens in the algorithm, which is the array of value above.
https://crdt-woot.herokuapp.com/
It's more of a proof of concept, which would need some more improvements in order to be production ready.
- Implementation of CRDT WOOT, a collaborative editing algorithm
FluidFramework
- FluidFramework: Build distributed, real-time collaborative web applications
-
Ask HN: What Are You Working on This Year?
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...
- Ask HN: Apps that are built with Git as the back end?
- Realtime: Multiplayer Edition
- Fluid Framework: Data Sync Reimagined
-
Woe be onto you for using a WebSocket
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:
-
Microsoft Launches Google Wave
(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](https://github.com/microsoft/FluidFramework/blob/main/LICENS...) 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](https://fluidframework.com/docs/deployment/service-options/) 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.
-
The Lost Apps of the 80s
Within the context of the Microsoft-verse, Fluid Framework (https://fluidframework.com) is supposed to be solving similar problems in web apps, although I haven't personally played with it.
-
A couple of questions about dotnet from a Java developer :)
Microsoft recently open sourced fluid framework. It is a distributed, consensus based, real time collaboration framework written in typescript. Fluid would keep your clients synced up and your server code would only have to handle when someone hits submit. Fluid Framework
-
Fluid Framework discovery
The official documentation and the github repository seem clear.
What are some alternatives?
yjs - Shared data types for building collaborative software
SyncedStore - SyncedStore CRDT is an easy-to-use library for building live, collaborative applications that sync automatically.
teletype-crdt - String-wise sequence CRDT powering peer-to-peer collaborative editing in Teletype for Atom.
automerge - A JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically.
osmosis-js - JS reference implementation of Osmosis, a JSON data store with peer-to-peer background sync
Joplin - Joplin - the secure note taking and to-do app with synchronisation capabilities for Windows, macOS, Linux, Android and iOS.
dotted-logootsplit - A delta-state block-wise sequence CRDT
Command Line Parser - The best C# command line parser that brings standardized *nix getopt style, for .NET. Includes F# support
Matrix-CRDT - Use Matrix as a backend for local-first applications with the Matrix-CRDT Yjs provider.
crdt-event-fold - A Haskell library providing a garbage collected CRDT event accumulation datatype.
rsocket-java - Java implementation of RSocket
jsynchronous - Jsynchronous.js - Data synchronization for games and real-time web apps.