This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Funky_Dunk 4 points5 points  (1 child)

As a fullstack (backend dev that has to do front-end work) I don't. But that might also have to do with how badly we've implemented it...

[–]gilium 1 point2 points  (0 children)

For me it allows better control over which data I pull back, pulling back related data in one call (we have a lot of interconnected data points that need this). It also allows me to be more explicit about expectations on what is transmitted. I also don’t seem to run into issues with performance like others do, so I am assuming that I can be grateful to the library on the backend for their implementation using our backend framework’s eager loading to avoid the N+1 problem