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
Just a general question I am curious with the mesh. And I am not talking about Docker vs on GCP, etc ... just automation.
We have multiple microsevices (one deployment unfortunately tied to the web page for now) that has either GraphQL/OpenApi/GRPC downstream that gets meshed in.
Steps Right Now:
Deploy Backend Services
Rebuild GraphQL Mesh so it can go off backend that was changed
Deploy GraphQL Mesh
my issue of course right now is the whole web layer being tied (which I will eliminate eventually)
But I hate I have to do 2 deployments. I thought of just having it build the .mesh directory off of stage, use the graphql contained there to build prod. And that way I can deploy it all at the same time.
When I looked a while back it seemed too much of the endpoints were hard coded in there.
I obviously dont want to yarn mesh dev in prod, since 1. its slower for pod restart 2. and more importantly if a svc was down and the pod restarted then it wouldnt come back up which would be super not good.
Was curious if anyone has better strategies? Would the use the stage graphql output be a good option? (obviously you would have to make sure all the svcs there got deployed)
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
-
Just a general question I am curious with the mesh. And I am not talking about Docker vs on GCP, etc ... just automation.
We have multiple microsevices (one deployment unfortunately tied to the web page for now) that has either GraphQL/OpenApi/GRPC downstream that gets meshed in.
Steps Right Now:
my issue of course right now is the whole web layer being tied (which I will eliminate eventually)
But I hate I have to do 2 deployments. I thought of just having it build the .mesh directory off of stage, use the graphql contained there to build prod. And that way I can deploy it all at the same time.
When I looked a while back it seemed too much of the endpoints were hard coded in there.
I obviously dont want to
yarn mesh dev
in prod, since 1. its slower for pod restart 2. and more importantly if a svc was down and the pod restarted then it wouldnt come back up which would be super not good.Was curious if anyone has better strategies? Would the use the stage graphql output be a good option? (obviously you would have to make sure all the svcs there got deployed)
Beta Was this translation helpful? Give feedback.
All reactions