Hacker GitHub

← All repos

planetscale/discussion

View on GitHub ↗ ★ 79

7 mentions on Hacker News by 1 person: 0 stories, 7 comments · first 2024-02-05 · latest 2024-07-14

Mentions per year 7 mentions · busiest year 2024 (7)
20082026
  1. …ranges or a central server allocating chunks are two popular methods that come to mind. [0]: https://github.com/planetscale/discussion/discussions/366
    comment by sgarland · 2024-07-14 · in ULID: Like UUID but Sortable (2019)
  2. …it can be done at scale), UUIDv7 is probably the best from a DB performance perspective. [0]: https://github.com/planetscale/discussion/discussions/366
  3. …at scale. As for auto-incrementing, there are plenty of solutions for distributed systems. [0]: https://github.com/planetscale/discussion/discussions/366
    comment by sgarland · 2024-06-05 · in You'll regret using natural keys
  4. …Don’t cause B+tree page splits, especially in an RDBMS with a clustering index like MySQL. [0]: https://github.com/planetscale/discussion/discussions/366
    comment by sgarland · 2024-04-11 · in The UX of UUIDs
  5. …periodically refreshed. PlanetScale uses int PKs [0], and they seem to have scaled just fine. [0]: https://github.com/planetscale/discussion/discussions/366
  6. …keys. They absolutely can scale, it just requires more thoughtful data modeling and queries. [0]: https://github.com/planetscale/discussion/discussions/366
    comment by sgarland · 2024-02-05 · in UUID v7
  7. …[1]: https://slack.engineering/scaling-datastores-at-slack-with-v... [2]: https://github.com/planetscale/discussion/discussions/366
    comment by sgarland · 2024-02-05 · in UUID v7