<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>dataloader on Washington Botelho</title><link>http://www.wbotelhos.com/tags/dataloader/</link><description>Recent content in dataloader on Washington Botelho</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 03 Aug 2021 00:00:00 -0300</lastBuildDate><atom:link href="http://www.wbotelhos.com/tags/dataloader/index.xml" rel="self" type="application/rss+xml"/><item><title>GraphQL with Absinthe on Phoenix - Query and Dataloader</title><link>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-query-and-dataloader/</link><pubDate>Tue, 03 Aug 2021 00:00:00 -0300</pubDate><guid>http://www.wbotelhos.com/graphql-with-absinthe-on-phoenix-query-and-dataloader/</guid><description>Updated at: Jul 23, 2023 One thing is true, GraphQL is here to stay. This query language is very useful since you can just declare the fields you can have, but choose what you want in each request. It&amp;rsquo;ll avoid you to create combinations of logic that return fields for different purposes.
Goal We&amp;rsquo;ll learn how to use GraphQL on Phoenix with the help of Absinthe and how to deal with Queries and how to avoid N + 1 with the help of Dataloader.</description></item></channel></rss>