Hi, and thanks for Goldiloader.
I have been a protagonist of fighting N+1 for a while:
I recently added Goldiloader support to N1Loader in v3.0.0, and the integration turned out very nicely.
N1Loader complements Goldiloader well for cases where users want Goldiloader’s automatic association loading, but also need lazy batched loading for things that are not regular ActiveRecord associations, such as:
- computed values
- custom loaders
- service/API calls
- GraphQL fields
- other N+1-prone derived data
The Goldiloader integration in N1Loader preserves Goldiloader context and supports isolated loaders, so the two gems work together naturally rather than overlapping awkwardly.
Would you be open to mentioning N1Loader somewhere in the Goldiloader README or docs as a companion gem for those cases? I think that could be useful for Goldiloader users who want to keep Goldiloader for associations and use N1Loader to cover the remaining N+1 gaps.
Hi, and thanks for
Goldiloader.I have been a protagonist of fighting N+1 for a while:
I recently added
Goldiloadersupport toN1Loaderin v3.0.0, and the integration turned out very nicely.N1Loader complements
Goldiloaderwell for cases where users wantGoldiloader’sautomatic association loading, but also need lazy batched loading for things that are not regular ActiveRecord associations, such as:The
Goldiloaderintegration inN1LoaderpreservesGoldiloadercontext and supports isolated loaders, so the two gems work together naturally rather than overlapping awkwardly.Would you be open to mentioning N1Loader somewhere in the
GoldiloaderREADME or docs as a companion gem for those cases? I think that could be useful forGoldiloaderusers who want to keepGoldiloaderfor associations and use N1Loader to cover the remaining N+1 gaps.