Comment by crabmusket

> This is getting dangerously and excitingly close to a graph database implemented in a relational database!

This feels like a great unresolved tension in database / backend design - or maybe I'm just not sophisticated enough to notice the solutions?

Is the solution event sourcing and using the relational database as a "read model" only? Is that where the truly sophisticated application developers are at? Is it really overkill for everybody not working in finance? Or is there just not a framework that's made it super easy yet?

Users demand flexible schemas - should we tell them no?