Earlier quoted context omitted.
This will work, but you risk referential integrity violations, as well as performance problems at scale. The main issue is what I said in “IME…” – tech debt builds, and people never want to go back and fix it. Just upsize the hardware, easy-peasy. I would rather see a wide table with a bunch of bools indicating various options, personally. When that gets annoying or unperformant, split it out into logical groups. Col…
Which is precisely the caveat I mentioned at the beginning: > and for example use jsonb columns and later move data out of it if you notice you need to query on it more performantly you can get very far. If you put data inside where you want the database to enforce integrity...then it's the wrong place for the data. If you are getting problems on scaling, you are relying on data in jsonb columns for heavy queries whi…
It should take a day at most to work out the data model for a startup. I don’t see that as a lot of overhead.
Do as you will, but from my perspective, I’d rather do it correctly from the start.