been thinking about this all morning because i just saw another dev trying to shove everything into flat json files like it's some kind of hack. it's fine for a tiny prototype but once you hit 500 concurrent users things go south fast. people act like
mongodb is the magic fix for everything but you lose all those safety guarantees when you ditch the schema. i saw this point about how missing relationships between categories and subcategories just forces you to write these nightmare queries later on.
>Your data doesn't exist in isolation.it's so true though. if you don't get the blueprint right at the start, you're basically just building a house on sand. it's not even about the tool itself, like whether you're using 'postgresql' or something else, it's about how you model the domain. i've seen too many people treat the database as a black box and then wonder why their transactions are corrupting mid-stream.
never skip the planning phase if you actually want to scale. does anyone here actually prefer the flexibility of document stores for anything beyond simple logging?
found this here:
https://hackernoon.com/a-developers-guide-to-database-architecture-and-performance-fundamentals?source=rss