learn-graphql VS artwork

The source code lives here https://github.com/hasura/learn-graphql/tree/master/tutorials/frontend/nextjs/app-final

Looking for feedback. The source code and the tutorial is all open source.

We at Hasura, along with the community have created a series of open source tutorials starting from GraphQL Basics, Hasura Basics to full fledged frontend tutorials in various frameworks. You name it, we have it :)

I am Praveen from Hasura. We first launched Hasura Learn in 2019 with the intention of building GraphQL tutorials for developers who wanted to learn GraphQL by getting hands-on, within the comfort of their favourite stacks. 2.5years later, we have grown this to just over 25 courses, added tutorials on databases, and Hasura (basics, authorization & production ready advanced concepts). We. have had a lot of help from the community in building & maintaining these over the years.

Hey, I maintain the learn-graphql repo. We have tutorials for GraphQL beginners, those who want to learn frontend integrations and those who want to learn backends via Hasura. If you are completely new to GraphQL, I would suggest you check out our GraphQL Basics tutorial. If you are looking to integrate GraphQL with frontend frameworks and learn hands on building an app, I would suggest you check out out Frontend tutorial series and choose the framework you are comfortable with.

I mean that! You don’t need a backend developer, at least for serving data. Hasura is making this pleasant to work with the data we have defined in the database editor. Helps us make relations, permissions and add some other useful features. More information you will find on their website.

Learn

They developed a solution, and open sourced it as GraphQL.

I'm using the Official GraphQL, HowToGraphQL and several other websites to curate my own notes on GraphQL.

Your cloud architecture, system design and project leadership skills should be more important than language specifics when interviewing. That being said, I recommend learning about Node.js internals (e.g. the event loop); ES6+ language improvements; and some trending tools and libraries like TypeScript, Docker, Serverless Framework and GraphQL. Know enough about Express and serverless functions justify using one over the other when designing a system.

API stands for Application Programming Interface. APIs define how two pieces of software can connect and talk to each other. If your application were a big company, your API's job would be to keep in touch with external parties (customers or company partners, for example). Most APIs are organized around some standard, like REST or GraphQL, so that everybody knows how to use them.

GraphQL is developed by Facebook initially for their mobile app and has been adopted widely across web apps.

Last week, I built a microservice: a resource for a section of the landing page of the platform, which renders from a database loaded with data. In technical terms, I built and consumed an API. I used Dynamo DB (a database provided by Amazon Web Services (AWS))) to store my data, creating a table with desired fields for me to use in populating my table. GraphQL was used as playground for me to query and mutate my database. i.e. a way of creating, reading, updating and deleting information from the database, a process technically known as CRUD.

GraphQL, if you are not familiar, is a way of having APIs which are query-able similar to SQL for a database.

GraphQL.org

More than that, it's a good idea for storing non-sensitive data across the application. It might be a Redux or GraphQL state or some global app-wide variables. On the other hand, you shouldn’t use that for storing tokens and secrets, as the storage is not encrypted in any way.

AWS AppSync is a fully managed GraphQL API which is a serverless offering by AWS.