ksuid
tbls
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ksuid
- What happens after 100 years?
-
Zero Downtime Postgres Upgrades
OP here - we avoid sequences in all but one part of our application due to a dependency. We use [KSUIDs][1] and UUID v4 in various places. This one "gotcha" applies to any sequence, so it's worth calling out as general advice when running a migration like this.
[1]: https://segment.com/blog/a-brief-history-of-the-uuid/
-
Bye Sequence, Hello UUIDv7
UUID v4 isn't large enough to prevent collisions, that is why segment.io created https://github.com/segmentio/ksuid which is 160bit vs the 128bit of a UUIDv4.
- You Don't Need UUID
- A Brief History of the UUID
-
Type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
Assuming you don't need to use UUIDv7 (or any UUID's) then https://github.com/segmentio/ksuid provides a much bigger keyspace. You could just append a string prefix if you wanted to namespace, but the chance of collisions of a KSUID is many times smaller than a UUID of any version.
-
Unexpected downsides of UUID keys in PostgreSQL
KSUID's are have temporal-lexicographical order plus 128 bits of entropy, which is more than UUIDv4.
https://github.com/segmentio/ksuid
-
UUIDs are so much better than autoincrementing ids and it's not even close
That's why you use ksuid (https://segment.com/blog/a-brief-history-of-the-uuid/) or, if you're willing to go with a draft spec you could go with the new UUID formats https://www.ietf.org/archive/id/draft-ietf-uuidrev-rfc4122bi...
-
What Happened to UUIDv2?
Interesting in more history of UUIDs? Twilio Segment's blog has an amazing history lesson about how they came to be.
-
Which UUID package do you use? and why?
I use the ksuid from segment. https://github.com/segmentio/ksuid
tbls
- FLaNK 25 December 2023
- tbls
- Tools to use to make high level Architecture diagrams
-
Graphviz: Open-source graph visualization software
Autogenerated database documentation is often pretty hit and miss but tbls[1] does a pretty good job in that space. Especially when you comment on your tables, fields, views, functions etc (which is a good habit anyway!) the output is quite useful
[1] https://github.com/k1LoW/tbls
-
Lesser Known PostgreSQL Features
In-database comments combined with something like https://github.com/k1LoW/tbls make for very cheap database documentation.
No affiliation with tbls except that I'm a big fan
-
Recommendations for a CLI-tool to generate DB diagrams?
Check out tbls. You can create a ERD in one command
What are some alternatives?
ulid - Universally Unique Lexicographically Sortable Identifier (ULID) in Python 3
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
pg-ulid - ULID Functions for PostgreSQL
prisma-client-go - Prisma Client Go is an auto-generated and fully type-safe database client
nanoid - A tiny (124 bytes), secure, URL-friendly, unique string ID generator for JavaScript
ulid-mssql - Implementation of ULID generator For Microsoft SQL Server
plantuml-syntax - vim syntax file for plantuml
python-ksuid - A pure-Python KSUID implementation
mermaid - Generation of diagrams like flowcharts or sequence diagrams from text in a similar manner as markdown
uuid7 - UUID version 7, which are time-sortable (following the Peabody RFC4122 draft)
postgres-elasticsearch-fdw - Postgres to Elastic Search Foreign Data Wrapper