Jazz – Apps with Distributed State

Re:Jazz – Apps with Distributed State by bbor on Monday October 07, 2024 @08:15PM (#41772525)

Plus the sync only works between clients AFAICT — literally all the listed backends are also “coming soon”. Which is troubling, I’d guess that almost all local-first applications need some sort of trusted verification server, at the very least. But maybe I’m biased/unimaginative; I suppose some kinds of collaboration apps (figma, google docs, etc) might work fine serverless? Certainly not games or AI agents, right?

This seems awesome, but my natural game-stopping questions are;

1. When will backends be supported?

2. Why doesn’t the site mention “local-first”?

Oh and just for fun;

3. Why “Collaborative Values” instead of what I learned in school, “Shared Memory”?

[ Parent | on HN ]

Re:Jazz – Apps with Distributed State by theanzelm on Tuesday October 08, 2024 @03:01AM (#41774480)

1. The sync is not just between clients, it by default works over a central backend infrastructure that syncs and persists. Plus you can create server workers (with jazz-nodejs) that also are clients to the same infrastructure and can do side-effects like API calls and interacting with “normal” databases in response to react state changing. And they can also mutate Jazz state.

2. The next version will. I like to think of Jazz as distributed state, of which local-first is a special case.

3. Shared memory to me sounds like concurrency is handled with locks, while Jazz uses CRDTs

[ Parent | on HN ]