one simple thing that would enable stronger consistency is where you expose the event sequence number to clients so they can just store the latest and pick up on a sync from that point without wasting any bandwidth

negentropy is so retardedly stupid in that respect, but it was invented to work around the lack of easy extension of the interface because it was made so complex and brittle

Reply to this note

Please Login to reply.

Discussion

Yeah if you added a sequence you'd have an event queue.

Relays could be an open alternative to Amazon SQS/SNS.

Maybe we need a whole new kind range for sequenced events, as those would probably require a different implementation in the relay code.

no, sequence numbers are completely subjective to a relay, they are literally a record of when they saw an event

i already implemented it, go look:

https://realy.mleku.dev/api#tag/events/GET/api/eventidsbyserial/{start}/{count}

yes it was that simple

and btw, the fact that i came up with it in collaboration with semisol is part of why i'm so salty about his behaviour

anyway, it's in there, and i put it there *so he could sync faster with realy*, you see the tone of that?

did you just describe kafka?

and RabbitMQ, and NATS JetStream

oh look it’s all message queues and write ahead logs

XD yup

We have kafka, at work, so probably.