Downsides of Offline First

• absurd-sql

  24 4,050 2.5 JavaScript

  sqlite3 in ur indexeddb (hopefully a better backend soon)

It's infuriating to me that WebSQL was killed. 99% of real-world data is relational and yet the powers that be decided that we should all be forced to use IndexedDB and hacky layers like PouchDB built atop it.

I'm exciting about https://github.com/jlongster/absurd-sql though.

• standards-positions

  178 595 7.6 Python
  

> there should be a way to request permission to store data that isn't deleted except for explicit action by users

I think that's "request permission to use files on disk". This is in progress as https://developer.mozilla.org/en-US/docs/Web/API/File_System..., though there's still more work before there's a version all the browsers like (Mozilla likes the ability to work with files, but thinks cross-site access should not be included: https://mozilla.github.io/standards-positions/#native-file-s...)

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• noms

  11 7,502 1.9 Go

  Discontinued The versioned, forkable, syncable database

  

Not much more to say other than Noms was my favorite project (https://github.com/attic-labs/noms) for a while until acquisition and the engineers are now the ones behind Replicache (https://replicache.dev/).

I think this is going to be the next "Realm" that works everywhere.

• offix

  2 771 0.0 TypeScript

  Discontinued GraphQL Offline Client and Server

  

Yeah,I'm trying to implement an electron offline first app that syncs, there seems to readymade solution.

Stuff like https://github.com/aerogear/offix seem to be in the right direction of what I'm looking for but not nearly mature enough.

I don't want to pu to much effort on the app so I would like something more or less ready made, preferably with graphql apis.

Any suggestions welcome.

• crdt-example-app

  2 567 0.0 JavaScript

  A full implementation of CRDTs using hybrid logical clocks and a demo app that uses it

* https://www.youtube.com/watch?v=DEcwa68f-jY

And his demo implementation (and annotated fork):

* https://github.com/jlongster/crdt-example-app

• distributed-counters

  1 6 10.0 Erlang

  Experiments with distributed counters

I was also a "true believer" in CRDTs for a long time, implementing my first ones in Erlang about 9 years ago[1], but my opinion of where they fit has changed significantly.

The one issue with CRDT that I find is rarely mentioned and often ignored is the case where you've deployed these data structures that include merge logic to a set of participating nodes that you can't necessarily update at will. Think phones that people don't update, or IOT/sensor devices like electric meters or other devices "in the wild".

When you include merge logic – really any code or rules that dictate what happens when the the data of 2 or more CRDTs are merged – and you have bugs in this code running on devices you can never update, this can be a huge mess. Sure you can implement simple counters easily (like the ones I linked to), and you can even use model checking to validate them. But what about complex tree logic like for edits made to a document? Conflict resolution logic? Distributed file system operations? These are already very complex and hard to get right without multiple versions involved and unfixable bugs causing mayhem.

Having to deal with these bugs in the context of a fleet of participants on a wide range of versions of the code, the combinatorial explosion of the number of possible interactions and effects of these differing versions and bugs taken together can really become impossible to manage.

I'd be interested to hear from folks who have experience with these kinds of issues and how they have dealt with them, especially if they are still convinced that CRDTs were the right choice.

[1] https://github.com/nicolasff/distributed-counters

• shelf

  2 52 0.0 JavaScript

The CRDT I was referencing was Shelf by Greg Little. He's given a few talks about it at the braid meetups. When he first showed it off, Kevin Jahns (the Yjs author) was also there and was as impressed as I was:

https://braid.org/meeting-8

The code is all here. Its tiny:

https://github.com/dglittle/shelf

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project