Home
Feed

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "How Twitter generates millions of unique ids per second?" | Hashnode

Feed/

Discussion

How Twitter generates millions of unique ids per second?

A note on system design of generating unique ids per second.

Feb 4, 2022·5 min read·blog.sagarmoy.workRead the article

#distributed-system
#system-architecture

Written by

Sagar

@sagars01 · Bengaluru

View profile

Staff Software Engineer with 10 years of building, breaking and gliding in the tech world

Staff Software Engineer experienced in building highly scalable software. Currently on mission to help frontend engineers move into fullstack engineering roles

Responses1

Markdown supported · ⌘↵ to post

Miki Szeles

Feb 4, 2022

Interesting insights Sagar. Thanks. I am not an expert on the topic, so my question might be stupid: Why do we need a sortable id? Why don't we simply sort based on the creation timestamp?

Sagar

Feb 4, 2022

Hello Miklós, Thank you for your kind words, means a lot to me.

Now to answer your question in short.

Sortable UID are far more more easier to sort and you can set your index based on the uid’s timestamp.

Though you’re correct that we can store the timestamp in a tuple and sort based on it, but running that query will be a costly operation.

Miki Szeles

Feb 4, 2022

Thanks for the answer Sagar Sengupta