Evolving clock sync for distributed databases (opens in new tab)

> YugabyteDB is the first—and only—100% open-source, hybrid, multi-cloud, distributed SQL database on the planet.

It might be worth pointing out that HCL are patented by Cloudera in 2014 (with a provisional patent application filed in 2013) https://www.freepatentsonline.com/y2015/0156262.html

So while it is 100% open source, depending on your jurisdiction, you could be sued by Cloudera for patent infringement.

It is interesting, also how the referenced paper https://cse.buffalo.edu/tech-reports/2014-04.pdf is from 2014. Wonder if they knew about it each other? It doesn't seem like the researchers from the paper are mentioned in the patent at all.

I find these articles (and there are dozens of them) somewhat frustrating because they fundamentally misrepresent the role of time sync in distributed databases like Spanner. Spanner doesn't get correctness from tight synchronization, it gets low latency from that. Spanner's correctness comes from estimating the clock error of cluster participants and evicting them when necessary. You can have the latter property without the former, and having the former property without the latter is useless.

Yugabyte ensures transactions consistency for a ACID model in a linear clock synchronization between nodes. Great article!

Oh joys, the sound of re-inventing the wheel. The old "not invented here" syndrome.

Per the blog, they state they want max 7ms difference between nodes.

I'm no timesync guru, but AFAIK can do that off-the-shelf today using chrony with hardware timestamping or PTP. No need to invent your own.

And if you still insist on doing something different, why not work on improving the existing work being done under the the Open Compute Time Appliance Project (https://www.opencompute.org/projects/time-appliances-project...).