walrus
FluidFramework
walrus | FluidFramework | |
---|---|---|
5 | 12 | |
116 | 4,611 | |
0.0% | 0.1% | |
2.2 | 10.0 | |
5 months ago | 4 days ago | |
PLpgSQL | TypeScript | |
Apache License 2.0 | 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.
walrus
-
Realtime: Multiplayer Edition
Wen Bo from the Supabase Realtime team here!
We actually use https://github.com/supabase/walrus to get the database changes and we're planning on moving to a Rust worker (https://github.com/supabase/walrus/tree/worker/worker) for better performance especially in the RLS-enabled use case.
I promised José that I would check out Postgrex.ReplicationConnection and we might add it in to our Supabase Realtime some time in the future.
-
Multiplayer Demo Built with Elixir
[0] https://supabase.com [1] https://github.com/supabase/realtime [2] https://github.com/eulerto/wal2json [3] https://github.com/supabase/walrus [4] https://gsd.di.uminho.pt/members/cbm/ps/delta-crdt-draft16ma... [5] https://supabase.com/blog/2022/04/01/supabase-realtime-with-... [6] https://fly.io [7] https://github.com/supabase/realtime/tree/multiplayer [8] https://github.com/supabase/supabase/tree/master/docker
- Show HN: Multiplayer Demo Built with Elixir
-
PostgreSQL 14 Released
[Supabase cofounder] thanks for the kind words.
We're about to wrap up Row Level Security on our real-time APIs too[0] - soon you'll be able to use Policies universally on all APIs.
[0] https://github.com/supabase/walrus
-
Supabase limitations ? Any reasons not to use?
We are adding this to the database now: https://github.com/supabase/walrus
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?
symmetric-ds - SymmetricDS is database replication and file synchronization software that is platform independent, web enabled, and database agnostic. It is designed to make bi-directional data replication fast, easy, and resilient. It scales to a large number of nodes and works in near real-time across WAN and LAN networks.
SyncedStore - SyncedStore CRDT is an easy-to-use library for building live, collaborative applications that sync automatically.
pgvector - Open-source vector similarity search for Postgres
automerge - A JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically.
wal2json - JSON output plugin for changeset extraction
Joplin - Joplin - the secure note taking and to-do app with synchronisation capabilities for Windows, macOS, Linux, Android and iOS.
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
Command Line Parser - The best C# command line parser that brings standardized *nix getopt style, for .NET. Includes F# support
zombodb - Making Postgres and Elasticsearch work together like it's 2023
crdt-event-fold - A Haskell library providing a garbage collected CRDT event accumulation datatype.
mria - Asynchronously replicated Mnesia-like database for Erlang/Elixir
rsocket-java - Java implementation of RSocket