peterbourgon

3 ms·

1. 1.▲
   by peterbourgon 7y ago

   > even with synced clocks some will always be faster and always win writes. That's true, but, in the use cases that Roshi targets, it's also not a problem. Users will notice and re-issue writes.
2. 2.▲
   by peterbourgon 7y ago

   > If the clock skew is only off by a few seconds or even minutes, the impact isn't so horrible, but if the clock jumps ahead by 20 years, you've effectively prevented any writes to that key for 20 years. That's true, but (
3. 3.▲
   by peterbourgon 7y ago

   > That sounds like a great way to produce a bad UX where a computer with clock drift doesn't successfully write. With real world clock drift, this can be on the order of years That's true, but any reasonable datacenter operatio
4. 4.▲
   by peterbourgon 7y ago

   Principal author here. > a time series CRDT is... just an append-only log, sure you can call it a CRDT, but it doesn't really have any meaningful properties. So what's the point of calling this a CRDT? I'm confused by this