3 ms·

People might remember this showing up once or twice before as Replicache. Reflect adds a fully managed, incredibly fast sync server. The local-first/realtime s

People might remember this showing up once or twice before as Replicache. Reflect adds a fully managed, incredibly fast sync server. The local-first/realtime space is getting busy these days. Replicache/Reflect is well worth checking out for the beautifully simple data model / coding model. I'm very happy with it. One plus point compared to CRDTs is that you get to decide how you want to deal with conflicts yourself, with simple, sequential code. I'm not up to date with the latest in CRDT-land but I believe it can be complicated to add application specific conflict resolution if the built-in rules don't fit your needs.

dang 3y ago
Ah thanks - related past threads: A JavaScript framework to build offline-first but collaborative webapp - https://news.ycombinator.com/item?id=33269440 https://news.ycombinator.com/item?id=33269440 - Oct 2022 (2 comments) Linear clone, with realtime sync and instant UI - built with Replicache - https://news.ycombinator.com/item?id=31331660 https://news.ycombinator.com/item?id=31331660 - May 2022 (3 comments) Replicache: Easy Offline-First for Existing Applications - https://news.ycombinator.com/item?id=22173500 https://news.ycombinator.com/item?id=22173500 - Jan 2020 (22 comments)
ochiba 3y ago
> One plus point compared to CRDTs is that you get to decide how you want to deal with conflicts yourself, with simple, sequential code. I'm not up to date with the latest in CRDT-land but I believe it can be complicated to add application specific conflict resolution if the built-in rules don't fit your needs. I agree wholeheartedly — we took the same approach for PowerSync with a server reconciliation architecture [1] over CRDTs, which is also mentioned elsewhere in the comments here. For applications that have a central server, I think the simplicity of this kind of architecture is very appealing. Props to Aaron for bringing awareness to and evangelizing server reconciliation. [1] https://www.gabrielgambetta.com/client-side-prediction-server-reconciliation.html https://www.gabrielgambetta.com/client-side-prediction-serve...

dang 3y ago

Ah thanks - related past threads: A JavaScript framework to build offline-first but collaborative webapp - https://news.ycombinator.com/item?id=33269440 https://news.ycombinator.com/item?id=33269440 - Oct 2022 (2 comments) Linear clone, with realtime sync and instant UI - built with Replicache - https://news.ycombinator.com/item?id=31331660 https://news.ycombinator.com/item?id=31331660 - May 2022 (3 comments) Replicache: Easy Offline-First for Existing Applications - https://news.ycombinator.com/item?id=22173500 https://news.ycombinator.com/item?id=22173500 - Jan 2020 (22 comments)

ochiba 3y ago

> One plus point compared to CRDTs is that you get to decide how you want to deal with conflicts yourself, with simple, sequential code. I'm not up to date with the latest in CRDT-land but I believe it can be complicated to add application specific conflict resolution if the built-in rules don't fit your needs. I agree wholeheartedly — we took the same approach for PowerSync with a server reconciliation architecture [1] over CRDTs, which is also mentioned elsewhere in the comments here. For applications that have a central server, I think the simplicity of this kind of architecture is very appealing. Props to Aaron for bringing awareness to and evangelizing server reconciliation. [1] https://www.gabrielgambetta.com/client-side-prediction-server-reconciliation.html https://www.gabrielgambetta.com/client-side-prediction-serve...