pg-ulid
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.
pg-ulid
-
Lesser Known PostgreSQL Features
Here's one[1], not actively maintained though.
[1] https://github.com/edoceo/pg-ulid
-
PostgreSQL UUID vs. Serial vs. Identity
Yeah, just use a UUID unless the bits to store the UUID really are your driving limitation (they're not), having a UUID that is non-linear is almost always the most straight-forward option for identifying things, for the tradeoff of human readability (though you can get some of that back with prefixes and some other schemes). I'm not going to rehash the benefits that people have brought up for UUIDs, but they're in this thread. At this point what I'm concerned about is just... what is the best kind of UUID to use -- I've recently started using mostly v1 because time relationship is important to me (despite the unfortunate order issues) and v6[0] isn't quite so spread yet. Here's a list of other approaches out there worth looking at
- isntauuid[1] (mentioned in this thread, I've given it a name here)
- timeflake[2]
- HiLo[3][4]
- ulid[5]
- ksuid[6] (made popular by segment.io)
- v1-v6 UUIDs (the ones we all know and some love)
- sequential interval based UUIDs in Postgres[7]
Just add a UUID -- this almost surely isn't going to be what bricks your architecture unless you have some crazy high write use case like time series or IoT or something maybe.
[0]: http://gh.peabody.io/uuidv6/
[1]: https://instagram-engineering.com/sharding-ids-at-instagram-...
[2]: https://github.com/anthonynsimon/timeflake
[3]: https://en.wikipedia.org/wiki/Hi/Lo_algorithm
[4]: https://www.npgsql.org/efcore/modeling/generated-properties....
[5]: https://github.com/edoceo/pg-ulid
[6]: https://github.com/segmentio/ksuid
[7]: https://www.2ndquadrant.com/en/blog/sequential-uuid-generato...
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?
ksuid - K-Sortable Globally Unique IDs
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
cuid - Collision-resistant ids optimized for horizontal scaling and performance.
Dapper - Dapper - a simple object mapper for .Net
prisma-client-go - Prisma Client Go is an auto-generated and fully type-safe database client
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
plantuml-syntax - vim syntax file for plantuml
timeflake - Timeflake is a 128-bit, roughly-ordered, URL-safe UUID.
mermaid - Generation of diagrams like flowcharts or sequence diagrams from text in a similar manner as markdown
postgres-elasticsearch-fdw - Postgres to Elastic Search Foreign Data Wrapper