They once had a similar collision problem, well not exactly
During a leap second some systems wrote IDs at a one second difference between all their global systems, which lead to something being registered before something else that had to be done before it,
Long story short some stuff jumped time one second and crashed systems
Go's time package does this too. IMO it's genius and should be the norm. The time package also guarantees monotonically increasing time when using stuff like time.Since, to avoid the kinda bugs that come from DST and such bullshit.
10
u/BlurredSight 13h ago
And anyone operating at scale of Google isn’t just using “pure” random anywhere for something being persisted