3 ms·
I'm 100% with you on everything you said. It's too bad I've seen many JavaScript devs do queries in loops. Queries that can easily be batched. It's interesting
by nesarkvechnep 6y ago
I'm 100% with you on everything you said. It's too bad I've seen many JavaScript devs do queries in loops. Queries that can easily be batched. It's interesting for me what's the cause for this low level of relational database understanding.
- breatheoften 6y agoThis is not a javascript only phenomenon... I regularly encounter code running off of performance cliffs like this in rails application i'm working on -- and it's incredibly difficult to climb the application out of these cliffs ...
- jatone 6y agoi see it a bunch with activerecord like ORMS. the devs are just too lazy to care and it drags entire systems down.
- nesarkvechnep 6y agoYes, it's a problem in rails too. My current project is a rewrite (in Node) of big rails monolith which is full of synchronous http requests and SQL queries in loops. The sad thing is senior Node developers just port the code, seeing no problems with the aforementioned be.