3 ms·
Nice work! I'm curious, if you don't mind my asking. What are you building that requires that amount of scale? These are heavy hitting IDs (but of course you k
by echelon 6y ago
Nice work!
I'm curious, if you don't mind my asking. What are you building that requires that amount of scale? These are heavy hitting IDs (but of course you know that).
- social_quotient 6y agoMaybe they need the distribution part and not the scale. But I’m curious now too.
- abahlo 6y agoThanks and I don't mind at all! To be honest for the application I didn't want to expose a database serial (otherwise you'd know you're user #100, for example) or use UUIDs, so it's less about scale and more about obscuring ids. The library is well suited for huge scale scenarios nonetheless.
- LaundroMat 6y agoWhy did you not want to use UUID's?
- abahlo 6y agoI already use UUIDs for various fields and didn't want the id to be confused with other fields. More of a clarity/style decision than technical.
- tinus_hn 6y agoUnfortunately this means you get to make the same mistake as originally made with UUID: the static machine ID is a privacy leak.
- abahlo 6y agoIs it? Not sure private ips are so sensitive, esp. the lower parts.
- tinus_hn 6y agoIf it’s unique it’s a privacy leak. I’m not going to debate that, it’s common knowledge. UUID was changed in the 90s to be a hash of this instead and later to just be a completely random number because there are so many bits the likelihood of a single duplicate being generated before the sun has swollen enough to consume the earth is slim so you don’t actually need these schemes to provide a unique number.
- deleted 6y ago[deleted]