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’…
Show HN: ChartDB Cloud – Visualize and Share Database Diagrams
11–16 of 16 posts
Re: Show HN: ChartDB Cloud – Visualize and Share Database Diagrams
#12Earlier quoted context omitted.
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 marke…
how many tables? is it manageable and interesting like trying to squeeze 2b records into postgres or what? Also lucidchart is just draw.io fyi - you don't need a license unless you need the file sharing aspect and I feel like it belongs closer to the code. I'm just generally curious what others' process is for this as the only meetings I've had in the last 5 years were who was getting cut.
> Also, Lucidchart is just draw.io fyi - you don't need a license unless you need the file sharing aspect, and I feel like it belongs closer to the code.
No, it is not. I took the whole day to check what is available in the market, and concluded that Lucidchart UX is quite balanced.
Re: Show HN: ChartDB Cloud – Visualize and Share Database Diagrams
#13Re: Show HN: ChartDB Cloud – Visualize and Share Database Diagrams
#14Re: Show HN: ChartDB Cloud – Visualize and Share Database Diagrams
#15Pretty. 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’…
If I care about the data model so much that I want to diagram it then it's going to be the exact DB schema.
Re: Show HN: ChartDB Cloud – Visualize and Share Database Diagrams
#16Earlier quoted context omitted.
how many tables? is it manageable and interesting like trying to squeeze 2b records into postgres or what? Also lucidchart is just draw.io fyi - you don't need a license unless you need the file sharing aspect and I feel like it belongs closer to the code. I'm just generally curious what others' process is for this as the only meetings I've had in the last 5 years were who was getting cut.
If I recall, Lucidchart allows up to 15 "shapes. > Also, Lucidchart is just draw.io fyi - you don't need a license unless you need the file sharing aspect, and I feel like it belongs closer to the code. No, it is not. I took the whole day to check what is available in the market, and concluded that Lucidchart UX is quite balanced.