How to architecture umbrella project around Absinthe and its ecosystem?

yeah this is the sore spot that I was alluding to in my earlier post, and is something that I’ve personally experienced as well. @jfrolich was investigating an alternative/enhanced api that would make using dataloader between domain apps much more pleasant/useful, but I’m not sure if he’s still continuing that investigation: WIP: Deferrable dataloader by jfrolich · Pull Request #21 · absinthe-graphql/dataloader · GitHub

Also, here’s another related thread (that I posted a while back): A comprehensive approach to data loading and permissions