<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GraphQL on code.kiwi.com</title><link>https://code.kiwi.com/tag/graphql/</link><description>Recent content in GraphQL on code.kiwi.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 24 Mar 2023 17:40:48 +0000</lastBuildDate><atom:link href="https://code.kiwi.com/tag/graphql/index.xml" rel="self" type="application/rss+xml"/><item><title>GraphQL 101 Challenge</title><link>https://code.kiwi.com/articles/graphql-101-challenge/</link><pubDate>Wed, 15 Jul 2020 18:47:00 +0000</pubDate><guid>https://code.kiwi.com/articles/graphql-101-challenge/</guid><description>&lt;h2 id="a-practical-introduction-to-graphql-not-only-for-qa-engineers"&gt;A practical introduction to GraphQL (not only) for QA engineers&lt;/h2&gt;&lt;p&gt;REST was born in 2000 as Roy Fielding wanted to define the standardized way of API communication. In 2015 Facebook internally developed GraphQL as a modern and scalable way of communication between client and server. &lt;a href="http://kiwi.com/"&gt;Kiwi.com&lt;/a&gt; adopted it for some products as well and in this article, you’ll understand in a practical way, what GraphQL is all about. You’ll learn:&lt;/p&gt;</description></item><item><title>Designing GraphQL schema for Kiwi.com: Part I. — Why?</title><link>https://code.kiwi.com/articles/designing-graphql-schema-for-kiwi-com-part-i-why/</link><pubDate>Wed, 13 Nov 2019 18:22:00 +0000</pubDate><guid>https://code.kiwi.com/articles/designing-graphql-schema-for-kiwi-com-part-i-why/</guid><description>&lt;p&gt;&lt;em&gt;This is the first part of a series about Designing a GraphQL schema for Kiwi.com.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;GraphQL schema design is important; this can be very well illustrated by our necessity to refactor some of the parts multiple times. Learn more in the following article by our Frontend Developer Jaroslav Kubíček.&lt;/p&gt;</description></item><item><title>Relay and GraphQL best practices</title><link>https://code.kiwi.com/articles/relay-and-graphql-best-practices/</link><pubDate>Wed, 10 Apr 2019 21:21:00 +0000</pubDate><guid>https://code.kiwi.com/articles/relay-and-graphql-best-practices/</guid><description>&lt;p&gt;&lt;em&gt;Check the videos from our internal, one-day workshop to learn more about proper usage and best practices around GraphQL and Relay.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src="https://code.kiwi.com/images/media/6b623cdcaeeb17361a6c3c70f467652f230ffd937b8763a17f2e4e7221abbb1f.webp" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Sharing is caring, that’s what triggered our internal one-day workshop which aim was to share knowledge between our JS developers. The goal of the first round was to show proper usage and best practices around GraphQL and Relay as we expect these technologies to be used more and more shortly.&lt;/p&gt;</description></item><item><title>Relay Modern data flow visualized</title><link>https://code.kiwi.com/articles/relay-modern-data-flow-visualized/</link><pubDate>Mon, 19 Mar 2018 11:04:00 +0000</pubDate><guid>https://code.kiwi.com/articles/relay-modern-data-flow-visualized/</guid><description>&lt;p&gt;When you start working with &lt;strong&gt;Relay Modern&lt;/strong&gt; it is really important to understand the &lt;strong&gt;data flow&lt;/strong&gt; concept first. I will explain this with some cute diagrams from my recent &lt;a href="https://www.meetup.com/BarcelonaJS/events/247277405/"&gt;BarcelonaJS&lt;/a&gt; talk. I hope you fall in love with Relay Modern after wrapping your head around its main idea.&lt;/p&gt;</description></item><item><title>IDX + GraphQL = ❤️</title><link>https://code.kiwi.com/articles/idx-graphql-%E2%9D%A4%EF%B8%8F/</link><pubDate>Fri, 23 Feb 2018 10:57:00 +0000</pubDate><guid>https://code.kiwi.com/articles/idx-graphql-%E2%9D%A4%EF%B8%8F/</guid><description>&lt;p&gt;&lt;a href="https://github.com/facebookincubator/idx"&gt;IDX&lt;/a&gt; is a library for accessing arbitrarily nested, possibly nullable properties on a JavaScript object. At least this is how it is described in the documentation. What does this mean in reality and why is it such a big problem in JavaScript? And why is it so important when working with GraphQL?&lt;/p&gt;</description></item><item><title>GraphQL pitfalls</title><link>https://code.kiwi.com/articles/graphql-pitfalls/</link><pubDate>Tue, 30 Jan 2018 10:31:00 +0000</pubDate><guid>https://code.kiwi.com/articles/graphql-pitfalls/</guid><description>&lt;p&gt;First of all, I love GraphQL and none of these pitfalls forced me to stop using it. Actually, I am trying hard to overcome these pitfalls by using it even more in order to find the best solutions and practices. But still, I’ve been faced with these challenging questions almost every day for more than a year and it makes me think.&lt;/p&gt;</description></item><item><title>GraphQL: Server-side Subscriptions</title><link>https://code.kiwi.com/articles/graphql-server-side-subscriptions/</link><pubDate>Mon, 15 Jan 2018 10:36:00 +0000</pubDate><guid>https://code.kiwi.com/articles/graphql-server-side-subscriptions/</guid><description>&lt;p&gt;OK, it’s 2k18 and everyone has already heard about GraphQL at least once. Maybe from your colleagues or even from some gopnik guys from the unfavourable areas of your city. GraphQL hype is everywhere.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://code.kiwi.com/images/media/11583a6cd915ccb0e79c91a276f36f459a832e2ba8559b7e2a2be0505315167b.webp" alt=""&gt;&lt;/p&gt;</description></item><item><title>Highlights from the React Day Conference</title><link>https://code.kiwi.com/articles/highlights-from-the-react-day-conference/</link><pubDate>Wed, 03 Jan 2018 10:49:00 +0000</pubDate><guid>https://code.kiwi.com/articles/highlights-from-the-react-day-conference/</guid><description>&lt;p&gt;The ecosystem around React itself is quite stable at the moment compared to the turbulent shifts that we’ve seen in recent years. &lt;em&gt;Declarativeness&lt;/em&gt; rules the code and GraphQL is a real game changer.&lt;/p&gt;
&lt;p&gt;In this article I’ve included some top picks to summarize the &lt;a href="http://reactday.berlin/"&gt;React Day Conference&lt;/a&gt; which took place in Berlin on December 2, 2017.&lt;/p&gt;</description></item></channel></rss>