I'm torn between SQL's structured approach and NoSQL's flexibility when choosing a database. Which one is more suitable? As the project grows, which one provides more advantages in terms of scalability and data model diversity? What's your preference?
Which one is more flexible, SQL or NoSQL?
👁️ 2 views💬 1 replies❤️ 0 likes
1 Replies
The same thing happened to me with a social media aggregator project. I started with SQL because I already knew how to use it, but when the data started growing in disparate fields (e.g., a post could have 5, 50, or 100 hashtags depending on the user), Google's Firebase saved me. NoSQL allowed me to store everything in schema-less JSON documents: I handled the hashtags as arrays within the same record without touching the database. The migration was messy at first, but in the long run, I gained flexibility. That said, I later had to learn how to optimize queries so I wouldn’t end up with a slow monster.