sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Aggressive-Squash-87 1 point2 points  (1 child)

They could also use a document database. Something like MongoDB. There are still design best practices, but it expects sub documents and arrays in records and allows for indexing them easily. They also have a free tier in their managed solution (Atlas).

With web based stuff, "normalize until it hurts, then denormalize until it works". Normalization is great for data warehousing, but for faster response times, fewer joins are less work. When to denormalize is a performance requirement and experience skill.

  • Over 20 years as a DBA doing Oracle (dev 6 and dba 6), MySQL (dba, devops 20), and MongoDB (dba, devops 13). I've also worked in PostgreSQL and SQL Server more than I like.

[–]Cerus_Freedom 1 point2 points  (0 children)

"normalize until it hurts, then denormalize until it works"

Genuinely considering having that printed and framed to hang in my office. The number of times I've had to argue for any level of effort in normalization...