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

# Subscription operations
GraphQL puts near real-time data, called **subscription operations**, at the same first-class level as queries or mutations. These subscriptions allow users to request data updates using the same semantics as any other GraphQL request and manage the life cycle of the data feed. Modern user interfaces using subscriptions can work with live data as a part of their normal conversation with a GraphQL server.

# Setting up subscriptions
Subscriptions let a client submit a GraphQL document that is executed based on some event in the system instead of being executed immediately. From the server’s perspective, we need to be able to hold onto documents that clients have submitted so we can run them at the right time. We also need a way to propagate events through the system. Finally, we need a way to have a persistent connection with the client so we can push results up to them when their documents are executed.

This requires a little bit of setup. Fortunately, **PlateSlate** already has _Phoenix_ as a dependency, which will play the publish-subscribe and WebSocket system. This provides several handy features for free. Clients will be able to use long polling or WebSockets. PubSub will work either over the distributed Elixir or through any other adapter built to work with Phoenix PubSub. However, there are a few things you need to do to connect these capabilities to Absinthe.

The first order of business is to add an `Absinthe.Subscription` supervisor to the PlateSlate application’s supervision tree by modifying the children list in the `start/2` callback of `application.ex`:

Learn how to use and setup subscriptions in GraphQL 

Subscriptions Setting

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

Subscriptions Setting

Subscription operations