You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hope I'm not overloading these discussion boards. I just ran into another topic for discussion, and I thought it'd be potentially helpful to mention it here.
I was wondering if you had any guidance on how best to deploy graphql-yoga when you're using the built-in node server. It seems pretty clear to me how I could cram it into Heroku or Render or something like that, but I have a vague concern that I would be missing some basic step and/or boilerplate.
Some specific questions I'm currently thinking over:
Could graphql-yoga fit nicely into a Vercel function? I see there is a minimal example of this. What are the limitations? When would I need to move to something larger?
Imagine that I am using graphql-yoga plus prisma. How does that change the considerations for a suitable deploy tool? Of course, a lot of this would necessarily live in the prisma documentation (use PG Bouncer, etc.). However, I suspect there is some unique graphql-yoga consideration as well (i.e. how does the app size change once you add data loaders?).
Imagine a word where I am building a monorepo. I have one project for a graphql api with a Prisma backend. I have a second project for a Next.js frontend. There are a few ways I can easily deploy this (Vercel, Netlify, and soon Render). What guidance would graphql-yoga have for optimal deploys?
I think the answer could be as simple at the Apollo Server documentation (which, more or less, says, "just do it").
Honestly, perhaps I am going too deep on "measure twice; cut once." Thanks in advance for any guidance.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi there,
I hope I'm not overloading these discussion boards. I just ran into another topic for discussion, and I thought it'd be potentially helpful to mention it here.
I was wondering if you had any guidance on how best to deploy
graphql-yoga
when you're using the built-in node server. It seems pretty clear to me how I could cram it into Heroku or Render or something like that, but I have a vague concern that I would be missing some basic step and/or boilerplate.Some specific questions I'm currently thinking over:
graphql-yoga
fit nicely into a Vercel function? I see there is a minimal example of this. What are the limitations? When would I need to move to something larger?graphql-yoga
plusprisma
. How does that change the considerations for a suitable deploy tool? Of course, a lot of this would necessarily live in theprisma
documentation (use PG Bouncer, etc.). However, I suspect there is some uniquegraphql-yoga
consideration as well (i.e. how does the app size change once you add data loaders?).graphql-yoga
have for optimal deploys?I think the answer could be as simple at the Apollo Server documentation (which, more or less, says, "just do it").
Honestly, perhaps I am going too deep on "measure twice; cut once." Thanks in advance for any guidance.
Beta Was this translation helpful? Give feedback.
All reactions