search

electric-sql / electric

Sync little subsets of your Postgres data into local apps and services.
https://electric-sql.com
Apache License 2.0
6.47k stars 156 forks source link

rename: `up-to-date` to `frontier`. #1959

Closed thruflo closed 3 days ago

netlify[bot] commented 2 weeks ago

Deploy Preview for electric-next ready!

Name Link
Latest commit 66b49437c9617ef5a12af76fcb57386da7319742
Latest deploy log https://app.netlify.com/sites/electric-next/deploys/672cde2e9b79060008dcb717
Deploy Preview https://deploy-preview-1959--electric-next.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

samwillis commented 1 week ago

I'd like to hold merging this until we chat a little about the difference between a differential dataflow frontier and what our up-to-date message does. While very similar, it doesn't do everything that the d2 version needs. If we are going to use d2 for stream processing we should just check that we don't want an additional message that meets the semantics required.

key difference is we send out up-to-data at the end of the LSN/"timestamp", with D2 they are at the beginning of them.

thruflo commented 1 week ago

I’m not particularly convinced that this PR is improvement. I think the idea that the up-to-date message indicates the data was up to date when the server generated it is valid/understandable and the term “up-to-date” is more readable and easier to generally talk about, when not in distributed systems edge case mode.

So perhaps we close this?