When HN users recommended it
1 HN user recommended this in 2016, in one comment.
20072026
Each tall tick is one HN user's first recommendation. A short tick is the same user again. Click a tick to jump to the comment.
Amazon's catalog no longer lists this product (checked 2026-11-02). The name comes from the link HN users posted.
1 HN user recommended this in 2016, in one comment.
Each tall tick is one HN user's first recommendation. A short tick is the same user again. Click a tick to jump to the comment.
> which requires having a GPS clock and an atomic clock on each datacenter,
Right. I'll download an open source database, then buy a commercial GPS clock and attach to it.
https://www.amazon.com/Spectracom-1200-033-SECURESYNC-MODULA...
Only $12k for a Spectracom. Granted they are nice.
Well, I guess if it demonstrates anything is one fact -- if even Google needed GPS hardware to provide "latest" in a distributed system, then OP is right. Time in distributed systems is very hard.
> Most designs simply rely on NTP or a similar time synchronization system.
Not sure if "simply" was mean sarcastic or not. If reliability and deletion of user's data is important, and it relies on getting NTP time, I would strongly advice not to use that distributed db system.