Dec 20, 2022·edited Dec 20, 2022

That's not "visualizing database", that is "visualizing database interactions", which is a completely different beast. Visualizing databases help scope the domain, visualizing interactions help scope the workload type. And they may or may not be within the realm of the same process.

Also, starting from top to bottom, most of the examples are actually too simplistic to be taken into account - when you have "user writes post" (I'm not even going to nitpick how that translates in your example to a select instead of an insert, but lets assume its not a user story), you are discarding context on purpose - user writes post WHERE? his timeline? a group? is it a comment post?

Is this relevant? Yup, because the simplistic graph examples don't work when you have a multi-level structure where you're posting to, or conditional rules to actually allow posting. Thing is, in *real life* you will often have database schemas (maybe visually), AND business rules, mapped independently, not this mish-mash. If you think I'm wrong, pick a simple social network (like eg. twitter) and try to map it using your approach, with consistent results.

Expand full comment