It's astonishing to me how difficult it (still) is to design a syncable local-first data model.
I keep thinking I've found a decent way, then realizing its flaws, then despondently noticing that the flaws were already discussed in Ink & Switch's article: inkandswitch.com/local-first.ht
Conversation
It’s really difficult. I’ve had success applying event sourcing to the problem, but schema evolution is a pain and it means my data model takes up a lot of my complexity budget
1
3
Replying to
Yeah, I'm using event sourcing on a custom transport/storage system now, and it's eating up *way* too much complexity.
In Mintter we have been working on this for more than a year... it is a challenge to ride the complexity..
Replying to
At least for me, the one saving grace is that this is very amenable to TDD and testing in general; easy+fast to replay events and then verify the final state
1
Yeah, that definitely helps, makes me feel much more comfortable.
I use event sourcing on based on that article. Helped a lot, and yeah it's really complex.
But I don't believe there's other alternative than that approach. Been researching about offline first for years too.
1