Last fall, Replicache commissioned Jepsen to take a look at their design docs, and we wrote a bit about how it works:

They're doing something kinda like Bayou for mobile apps: local, speculative JS transactions, which are available even offline, replicated asynchronously. Those transactions may be reordered/re-executed with varying effects, but always preserve causal ordering; eventually they stabilize on a fixed serial order.


Again, this is just design review--I can't speak to anything about Replicache's implementation--but these properties are theoretically achievable! There's precedent in both Bayou and Eventually-Serializable Data Services, both from 1996! I'm kinda curious what kind of cross-pollination was going on there.

Sign in to participate in the conversation

A single-user Mastodon instance for Jepsen announcements & discussion.