Set up Hasura GraphQL engine with YugabyteDB distributed SQL

Vladimir Novick
InstructorVladimir Novick
Share this video with your friends

Social Share Links

Send Tweet
Published 5 years ago
Updated 4 years ago

In this lesson we will see how you can run Hasura GraphQL engine on top of YugabyteDB Distributed SQL

YugabyteDB is an open source, high-performance distributed SQL database for powering global, internet-scale applications.YugabyteDB is also a cloud-native database, so it can be deployed across both public and private clouds, including Kubernetes environments. In regards to serving as a backend for microservices, YugabyteDB brings together three must-haves: a PostgreSQL-compatible SQL API, low-latency read performance, and globally distributed write scalability. YugabyteDB with its global data distribution brings data close to users for multi-region and multi-cloud deployments.

Vladimir Novick: [0:00] To get started, Yugabyte bin Hasura, we'll first create local Yugabyte cluster with a replication factor of three. We'll provide specific tserver flags, specify that we did want to suppress unsupported errors.

[0:27] Now that Hasura's on top of Yugabyte, I can use the docker run and specify port 8080. I also want to specify variance variable Hasura graphQL, database URL so I can point it to my postgres database.

[1:00] I will use both 5433 and Yugabyte database. I also need to specify another environment variable called Hasura graphQL, enable console. If I won't specify that, I won't be able to access the console locally.

[1:26] Now I want to specify the docker image that I wanted to use for this container so it will be Hasura/graphQL-engine:v1.2.1 or it can be latest image. Now if I go to docker ps, I will see that I have the engine is running.

[1:51] It started so I can now access to localhost:8080 and see it there. Let's go to localhost:8080 and I will see our Hasura Console is loaded.

egghead
egghead
~ 9 minutes ago

Member comments are a way for members to communicate, interact, and ask questions about a lesson.

The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io

Be on-Topic

Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.

Avoid meta-discussion

  • This was great!
  • This was horrible!
  • I didn't like this because it didn't match my skill level.
  • +1 It will likely be deleted as spam.

Code Problems?

Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context

Details and Context

Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!

Markdown supported.
Become a member to join the discussionEnroll Today