Sample Dockerfile to dockerize a Mesh project

[mnlbox]

Hi,

Can someone guide me on how can I dockerize a GraphQL Mesh project?
The doc here is not clear enough: https://the-guild.dev/graphql/mesh/docs/getting-started/deploy-mesh-gateway#mesh-and-docker

I just tried to run the build artifacts with node but it seems the built files are created in TypeScript so I guess I should use ts-node or something like that to run them or convert them to the executable *.js files then I can run them with node like node index.js or something like this.

Any idea?

[ardatan]

In Docker container, you don't need to setup ts-node. You can basically call mesh start to run the artifacts.

[mnlbox]

@ardatan OK got it. So the build output is not ready to use in production as a standalone app. It's better to compile that from TypeScript to JavaScript and turn the mesh output to an express/koa/nest/node application and use the bundled version based on javascript for production. Did I get correct?

[ardatan]

No, I didn't mean that. I meant the output itself is not a bundle or something like you expected to work without installing any other packages. It just generates the final schema with transformed sources to avoid future introspections and schema generations. The output is TypeScript still but mesh start handles the execution of TypeScript files for production.
There is no need for an additional fastify, express or whatever HTTP framework. mesh start gives you a pretty fast HTTP server based on uWS.js which is WAY faster than the regular Node http server. It is production ready.

I just recommended an alternative way for you in my previous message because you don't want to install any other dependencies and bundling is the only option available today for this use case.

[mnlbox]

Thanks, I think this is very important information to add to the docs maybe in a new section called "Mesh fundamentals or how Mesh works?" It was my first time reading somewhere that the Mesh server is based on uWS.js as an HTTP server for Mesh. If I'm not mistaken in the docs mentioned that Mesh uses Yoga and Envelop behind the scene. Also, the functionality of mesh start command is more clear for me now after your comment. So really thanks. 🌷

One last question about using Mesh with another HTTP framework. Do we still leverage the uWS.js and its fast HTTP Server in Mesh even when we are using the Mesh as a route handler inside another framework (for example, express or nest.js) like this:

const meshHandler = createBuiltMeshHTTPHandler();         <------------- Is this handler also fast and based on uWS.js?

  app.use("/mesh", (req, res) => {
    meshHandler(req, res);
  });

I mean is the handler returns from the createBuiltMeshHTTPHandler() also fast and based on uWS.js or uWS.js just used when we use mesh start command?
For example, if we use Fastify + Mesh is it faster compared to Mesh + Express, or does Mesh always use uWS.js, and then it's always fast, independent of the framework that we are using side by side of Mesh?

[ardatan]

Wait wait :D
Mesh's HTTP handler is a platform and environment agnostic HTTP handler that can be used with node:http, Express, Fastify, uWS.js and so on. So it allows you to use Mesh's HTTP logic outside of Mesh CLI. That's the first thing.

BUT, instead of an extra complex setup or configuring any other fancy frameworks, you can just use mesh start and enjoy Mesh API as-is.
You said you don't want to install extra dependencies so I didn't lead you to use uWS.js :)

So you will lose all the benefits of uWS.js if you use an extra setup with node:http or any other frameworks on top of it like Fastify or Express because uWS.js is completely a different implementation from node:http.

const meshHandler = createBuiltMeshHTTPHandler(); <------------- Is this handler also fast and based on uWS.js?

So, the answer is no.

For example, if we use Fastify + Mesh is it faster compared to Mesh + Express?

If Fastify is faster than Express, yes.

does Mesh always use uWS.js, and then it's always fast, independent of the framework that we are using side by side of Mesh?

HTTP handler itself has nothing to do with uWS.js. It is part of our CLI.

[mnlbox]

I see. I guess I got it now. 😃
Thanks for the clarification.