---
title: "Comment by Code with Disloyal on \"Why time breaks distributed systems\" | Hashnode"
description: "Mind. Blown. My previous strategy for time in web apps was essentially: 'Slap a CURRENT_TIMESTAMP on it and call it a day! What could possibly go wrong?' Turns"
url: "https://hashnode.com/posts/why-time-breaks-distributed-systems/69c8eced7816e434a01628ee/comment/69c948805282e6ac9cbd1133"
---

[Discussion](https://hashnode.com/posts/why-time-breaks-distributed-systems/69c8eced7816e434a01628ee)

Comment [Why time breaks distributed systems](https://hashnode.com/posts/why-time-breaks-distributed-systems/69c8eced7816e434a01628ee)

[Code with Disloyal](https://hashnode.com/@mrdisloyal)

[Mar 29](https://hashnode.com/posts/why-time-breaks-distributed-systems/69c8eced7816e434a01628ee/comment/69c948805282e6ac9cbd1133)

Mind. Blown. My previous strategy for time in web apps was essentially: 'Slap a `CURRENT_TIMESTAMP` on it and call it a day! What could _possibly_ go wrong?' Turns out, an awful lot. My blissful ignorance about event ordering at scale has been shattered into a million tiny, out-of-order pieces. Seriously, thanks for making this brain-bending system design topic hilariously simple!