<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ReactJS on Duomly blog</title><link>https://www.blog.duomly.com/it-ai-tags/reactjs/</link><description>Recent content in ReactJS on Duomly blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 08 Jul 2020 06:42:26 +0000</lastBuildDate><atom:link href="https://www.blog.duomly.com/it-ai-tags/reactjs/index.xml" rel="self" type="application/rss+xml"/><item><title>GraphQL tutorial - ReactJS Course: Lesson 1</title><link>https://www.blog.duomly.com/graphql-tutorial-reactjs-course/</link><pubDate>Wed, 08 Jul 2020 06:42:26 +0000</pubDate><guid>https://www.blog.duomly.com/graphql-tutorial-reactjs-course/</guid><description>&lt;h3 id="intro-to-reactjs-with-graphql"&gt;Intro to ReactJS with GraphQL&lt;/h3&gt;&#10;&lt;p&gt;REST is an API design architecture, where requests are done through the URLs, and the core idea in the REST API is that when linking to a particular URL, you should get a piece of data, called a resource. Connecting to the URL in the REST API is called a request, and the answer is the response.&lt;/p&gt;&#10;&lt;p&gt;GraphQL is a query language for the API. It allows us to ask for specific data, without calling the API a few times, and the request is done with queries. In case, developers need just one value from the database, there’s no need to get everything. GraphQL is organized as types and fields, not endpoints.&lt;/p&gt;</description></item></channel></rss>