Gain insights into crafting GraphQL APIs with Elixir's Absinthe. Explore building schemata, securing endpoints, and integrating frontends to master creating, publishing, and utilizing robust GraphQL APIs.

Craft GraphQL APIs in Elixir with Absinthe.png

graphql.tar.gz

Chapter_2_1_start

Chapter_2_2_object_Running_GraphQLServer

Chapter_2_2_object

Chapter_3_3_matching

Chapter_3_3_matching_GraphQiL

Chapter_4_2_Union_GraphQiL

Chapter_5_2_Create

Chapter_6_4-publish

Chapter_6_4-orderingapi

Chapter_7_5-default

Chapter_8_2-login

Chapter_8_3-context

Chapter_9_dataloader

Chapter_10_Start

Chapter_10_2_action

Chapter_10_3_put

Chapter_10_4_login

Chapter_10_5_History

Chapter_11_2_subsription

Chapter_11_1_start

Chapter_11_hybird

Chapter_11_Applo_Client

Chapter_11_1_start-Updated

Chapter11-2-HTTP-Subscription

Chapter11-2-HTTP-Relay-Subscription

GraphQL is an API query language that allows clients to ask for exactly what they need and nothing more makes it easier to evolve APIs over time.

This course is divided into three parts, Part 1- Build a GraphQL API, Part 2- Publish Your API, and Part-3 Use Your API. 

In the first part, you will cover topics ranging from basic GraphQL, Building GraphQL Schema, Taking User Input, Adding Flexibility, Making a Change with Mutations, and Going Live with Subscriptions.

In the second part, you will cover topics ranging from Resolution Middleware, Securing with Authentication and Authorization, and Tuning Resolution.

The third part will cover topics ranging from Driving Phoenix Actions with GraphQL, Integrating with the Frontend and GraphQL Types. Upon completing this course, you will have sufficient foundational knowledge of GraphQL, and you can build, publish and use your API in GraphQL.

Craft GraphQL APIs in Elixir with Absinthe

# On server-side

GraphQL query documents can be flexible because the server holds a complete schema that describes the shape of data modeled by the API. It also holds the input that it can expect from clients. As API developers, we are responsible for accurately building a representation of our data. If this sounds like a lot of effort, don't worry. The GraphQL server deals with the more mundane details in our business logic.

We’ll get into the nitty-gritty of how GraphQL schemas are built in the next chapter. However, let’s take a look at one of the most essential advantages that the GraphQL server provides: user input validation.


# User input validation in REST

Suppose, in our REST API, we have an endpoint that will return a list of upcoming events. We want to support filtering these events by the date and location where they will take place. This would give us something like this:

```
GET/events?date=2016-11-22&location_id=4
```

We can’t trust API users to give us correct input values. For example, the `location_id` could be “hello world” instead of a number. Or, the date could be given in an invalid or unsupported date format. Users might even pass superfluous parameters that they think should work but do not.

REST, as a standard, doesn’t have much to say about data validation. Hence, enforcing rules about incoming data is left to the code that handles the request code, which we have to write ourselves.

This validation code can add a lot of complexity to back-end controllers, which are often responsible for a long list of other tasks. These tasks include retrieving the information the client wants, formatting the result as the client expects, and sending the response back across the HTTP connection. This can quickly become a mess.

Learn GraphQL on the server-side and validate input using  RestAPI and GraphQL.

Server-side GraphQL

Getting Started

Meet GraphQL

Building Schema of GraphQL

Taking User Input

Adding Flexibility

Making a Change with Mutations

Going Live with Subscriptions

Resolution Middleware

Securing with Authentication and Authorization

Tuning Resolution

Driving Phoenix Actions with GraphQL

Integrating with the Front-end

Conclusion

Server-side GraphQL

On server-side