Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wanted to understand how to deploy graphql on AWS EC2 instances using graphql mesh and hive gateway #97

Closed
vibhor-d11 opened this issue Nov 5, 2024 · 3 comments
Labels
question Further information is requested

Comments

@vibhor-d11
Copy link

I have few doubts regarding using graphql mesh and deploying is using hive gateway without any subcription or cloud account of hive.

  1. I can create mesh config and can generate the graphql file using mesh. Will also create gateway config for caching etc.
  2. I can start the server using npx hive-gateway supergraph xyz.graphql, now if i write a script to run this server on a EC2 instance, it will serve as a graphql server right? Or do i need hive token etc to deploy it etc?
  3. Also their is Dashboard section with explorer, laboratory, are those features only for hive organisation membership? or it can be used without any membership and how? could not find any documentation or same.
  4. What is the best way to deploy it for best performance? using npx command and js package or as a express server or using binary cli etc?
@enisdenjo enisdenjo transferred this issue from graphql-hive/console Nov 11, 2024
@ardatan
Copy link
Member

ardatan commented Nov 11, 2024

  1. Yes that's how you should do!
  2. You can start the server exactly like that. You need Hive CDN Token if you use Hive CDN. If you need to report to Hive Dashboard, you need Hive Token. Other than, you don't need any token if you just want to serve your API.
  1. You can also self-host Hive Dashboard on your own too, if you don't want to sign up Hive.
    https://the-guild.dev/graphql/hive/docs/self-hosting/get-started
  2. For the best performance, you can use Hive Gateway CLI or our official Docker image. We recommend you to avoid any complicated server setup with Express etc.

@enisdenjo
Copy link
Member

Hey there! Thanks for writing. Let me jump straight in:

  1. GraphQL Mesh outputs a supergraph SDL that the Hive Gateway consumes. It does not generate a config file for the gateway.
  2. Hive Console (the dashboard) and Hive Gateway are separate products and can be used fully independently. So yes, you can serve any Federation supergraph without ever depending, or even having an account, on the Hive Console.
  3. All features of Hive Console (the dashboard) are available for every type of account. Here's the relevant documenation for the two:
    a. Explorer
    b. Laboratory
  4. The Hive Gateway CLI (npx hive-gateway) already has all performance related features implemented. You're recommended to use either the CLI or the official Docker image from this repo.

@enisdenjo
Copy link
Member

Oh, @ardatan beat me to it! @vibhor-d11 pick and choose. 😄

@enisdenjo enisdenjo added the question Further information is requested label Nov 11, 2024
@graphql-hive graphql-hive locked and limited conversation to collaborators Nov 15, 2024
@enisdenjo enisdenjo converted this issue into discussion #123 Nov 15, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants