Separate requests on frontend vs Join on backend - issue with backend dev

basically im working in a project in which backend uses very strange for me behaviour, instead of join on backend which i've seen in my recent projects that i worked with (im frontend dev with some backend exp.) - he gives us separate requests to "load" additional data on frontend, which causes simple list of tasks, make 4 requests per one task (100 requests per list with 25 tasks - default size) - that makes app load slowly, and for stupid things like images count i need to make additional fifth requests for example.

When i talked to him about that, he told me that its because of performance, and it behaves better that way, is faster, etc. - but he didn't test it, it sound for me like a wall-of, because he thinks his approach is best.

Can someone with experience guide me or tell me is it really better? App is loading sooo long rn. and data isnt complex, it does not have any multi-join data, it should be just task model with join of other data which contains foreig id of this task...

Am i wrong? Correct me if yes - db is on MYSQL, backend in .net

Thanks!

Continue reading...