3 ms·
That does sound like an engineering problem more than anything. On an off note, migrating to nosql might not have a lot of on paper benefit, but it does enforc
by Aperocky 2y ago
That does sound like an engineering problem more than anything.
On an off note, migrating to nosql might not have a lot of on paper benefit, but it does enforce developers to design their table and queries in a way that prevents this kind of query hell. Which might be worth it on its own.
- sgarland 2y agoHow does NoSQL (and which flavor are you referring to?) enforce that? RDBMS enforces it in that if you don’t do it correctly, you get referential integrity violations and performance issues. You’d think that would be enough to motivate devs to learn it, but no, let’s use more JSON columns!
- Aperocky 2y agoIt's the human aspect of engineering, you can't join 15 different tables just by running an 200 line SQL command in nosql and this manual burden forces a re-thinking in what the acceptable design is. relational DB is great, but just like java design pattern, it's being abused because it could be. People are happy doing stuff like that because it was low resistance and low effort, with consequences building up in the long term.
- whstl 2y agoIn my example the abuse was on the OOP part, not in the relational database part. Database joins were fine, they just weren’t being made in the database itself, due to absurd amounts of abstraction. I don’t disagree that rethinking the problem with NoSql would solve it (or maybe even would have prevented it), but on the other hand I bet having 5 layers of OOP could also mess up a perfect NoSql design.