Mesh dev in production

[belaczek]

What are the implications of using mesh dev in production compared to built gateway?
My goal is to implement a hot-reloading friendly gateway, which can reload and refresh on any schema change. With mesh build I'm hitting some limits in terms of performance and resource consumption

[ardatan]

See here;
https://the-guild.dev/graphql/mesh/docs/getting-started/deploy-mesh-gateway#deploy-mesh-with-mesh-start-on-nodejs
If you want to keep artifacts in a different place so artifacts would be dynamic, you can use this approach;
https://the-guild.dev/graphql/mesh/docs/handlers/graphql#fetching-sdl-or-introspection-from-cdn-or-any-other-schema-registry-tool

[belaczek]

Thank you, for quick response. So if I understand it correctly, cons of using dev server are only about slower startup (schemas have to be loaded and stitched) and more fragile startup, when one of the sources is down. Is that right? Are there any other downsides, considering that I do not have any use for generated ts typings?

[ardatan]

mesh dev generates types on each call even if you don't use them. Other than that, there is no other downside.