Comment by reactordev
Comment by reactordev 2 days ago
Pretty.
The question I have is this, and don’t attack me for asking, but do people still produce database diagrams for use at work? I thought we had abstracted this by using Domain Driven design, ORMs, APIs, and the like.
Do individual teams still document their tables or do they document their entities? Do you still hand roll sql in a dao or do you use some higher abstractions?
Curious minds want to know because it’s been over a decade since I’ve done any database design documentation and have only done lean relationships and domain modeling documentation. Swaggering the rest.
I will say this, I love the look of this and I would love to just draw abstract shapes and things like I do on Miro. AWS architectures, etc etc.
We do at my team. I do not work on the Backend side, but I help in designing the DB schema.
Whenever I am thinking of new features to be developed, or when engineers are suggesting some features/approaches, looking at the ERD helps a ton. Onboarding is also easier.
We were using Lucidchart[1] until we reached the limit[2], so we found dbdiagram.io (which is just not the same).
[1] So far, it was the best of the market in terms of "canvas freedom" [2] We are struggling with salaries, so we are saving everywhere