Message originally sent by slack user U7213XMGS3H
we think long term it probably makes sense for packs (and outside services) to have their own graphql schemas that get stitched together by something like apollo router
Message originally sent by slack user U7213XMGS3H
that’s all very speculative though
Message originally sent by slack user U70TIGAX94P
Yeah. That’s what we were moving towards too.
Message originally sent by slack user U70TIGAX94P
It made sense because some services were already looking to provide part of the main schema.
Message originally sent by slack user U70TIGAX94P
It‘s be cool though for systems that are purely monolithic to have a solution for stitching within the monolith.
Message originally sent by slack user U7213XMGS3H
What I was thinking was having each pack have it’s own GraphQL::Schema and GraphQL controller. The gateway wouldn’t know or care that these 2 endpoints were part of the same http service
Message originally sent by slack user U70TIGAX94P
yeah sure, you’d still need a separate gateway though. I do think it’s a viable path, but I wish we could just easily compose schemas directly in the rails app.
I realize I am late to the party…
I have so many questions and so many thoughts!
What do you all think of a regular video call time for discussions like this?
Message excluded from import.
Message excluded from import.
Message excluded from import.