metagration
FluidFramework
metagration | FluidFramework | |
---|---|---|
4 | 12 | |
100 | 4,611 | |
- | 0.1% | |
0.0 | 10.0 | |
about 2 years ago | 3 days ago | |
PLpgSQL | TypeScript | |
MIT License | 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.
metagration
-
Realtime: Multiplayer Edition
Realtime uses logical replication, and from your link it looks like it should work with Timescale (although not recommended):
> Using logical replication with TimescaleDB is not recommended, as it requires schema synchronization between the primary and replica nodes and replicating partition root tables, which are not currently supported.
As long as logical replication is supported, this won't be an issue for Realtime because the purpose is to receive data changes (which come in a JSON format) and the end-user doesn't need to persist schema modifications.
> but couldn't get it working
If you send me some error logs, I can take a look or forward to one of the team.
> support Postgres streaming replication
This is the first time I've heard it requested - I don't think it's something we'd do unless there was a good reason and strong demand. If we were to do any work in this direction we'd prefer to try contribute DDL streaming to PostgreSQL's logical streaming. We've been thinking about this for a while (Michel has built metagration - https://github.com/michelp/metagration which has prompted a few ideas for core patches)
- GraphJin – An Instant GraphQL to SQL Compiler
- Show HN: Metagration – Migrate Postgres with Postgres
- Metagration: PostgreSQL Migrator in PostgreSQL
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?
thin-backend - 🔥 Thin Backend is a Blazing Fast, Universal Web App Backend for Making Realtime Single Page Apps
SyncedStore - SyncedStore CRDT is an easy-to-use library for building live, collaborative applications that sync automatically.
pg_partman - Partition management extension for PostgreSQL
automerge - A JSON-like data structure (a CRDT) that can be modified concurrently by different users, and merged again automatically.
assert-combinators - Functional assertion combinators.
Joplin - Joplin - the secure note taking and to-do app with synchronisation capabilities for Windows, macOS, Linux, Android and iOS.
pg_graphql - GraphQL support for PostgreSQL
Command Line Parser - The best C# command line parser that brings standardized *nix getopt style, for .NET. Includes F# support
postgrest - REST API for any Postgres database
crdt-event-fold - A Haskell library providing a garbage collected CRDT event accumulation datatype.
thin-backend-todo-app
rsocket-java - Java implementation of RSocket