You must remember that caching in Magento works only when the fullpageCache option is turned on. Additionally, only the GET queries are cached, while the default query type sent by Apollo GQ is POST. That’s why the first change you’ll make should be changing the type of default requests. After that you can start optimizing query processing in Magento 2 by using the many functions and tools the Apollo GraphQL offers:<\/p>\n

\n
• InMemoryCache<\/strong><\/li>\n
• Cache managing \u2013 Fetch Policy<\/strong><\/li>\n
• persistCache library<\/strong><\/li>\n
• Middleware defining for GraphQL requests<\/strong><\/li>\n<\/ul>\n

  InMemoryCache<\/h4>\n

  This component lets you save the data in the browser window that has been downloaded from the server before. Thanks to that, the user returning to the site does not have to wait for the queries to be sent to the backend. Instead, the data is rendered instantly. Additionally, this tool allows you to cache whole requests and specific objects<\/strong>. What’s more, you can define a cache key for each and every object.<\/p>\n

  Cache managing with Fetch Policy<\/strong><\/h4>\n

  With this tool, you can define the type of caching policy for every query type. Already at the beginning, you have access to a few predefined policy schemas:<\/p>\n

  \n
  • cache-first \u2013\u00a0<\/strong>default cache policy in Apollo. This setting focuses more on fast response time than on retrieving the most up-to-date data.<\/li>\n
  • cache-and-network \u2013\u00a0<\/strong>this policy attempts to balance fast response time and in-cache data updates.<\/li>\n
  • network-only\u00a0<\/strong>\u2013 the point of this cache policy is to focus on updating the dating and caching the most up-to-date information while saving on query response time.<\/li>\n
  • cache-only \u2013\u00a0<\/strong>this policy saves the data without updating it.<\/li>\n
  • no-cache\u00a0<\/strong>\u2013 similar to network-only policy. It searches and retrieves the most up-to-date data, however, it does not update it itself.<\/li>\n<\/ul>\n

    All the data concerning the caching policies is stored in cache storage. However, after refreshing or reopening the site you’ll have to download it once again.<\/p>\n

    persistCache library<\/h4>\n

    Apollo GraphQL’s persistCache allows for dynamic content transfer between InMemoryCache and to local storage<\/i><\/strong>\u00a0module. What’s more, when the site is reopened the data is transferred again from the module to the InMemoryCache as initial state cache.<\/p>\n

    Middleware defining for GraphQL requests<\/h4>\n

    GraphQL equips you with the option of defining which middleware (software that lets two separate applications or systems communicate with each other) is going to be responsible for request authorization. This can be especially helpful when you encounter problems with your website loading. In this case, instead of showing an error notification, you can configure the middleware to forcefully repeat the request loading, while the app is showing the user the loading page.<\/p>\n

    You also have to remember that to gain access to Apollo GraphQL, you’ll have to configure Magento PWA Studio<\/strong>. This will allow for further optimization of GraphQL queries and server-to-client communication in Magento 2.<\/p>\n

    Magento 2 optimization: Advantages of GraphQL<\/h2>\n

    When comparing the two technologies that are GraphQL and REST, you can see certain advantages on the part of GraphQL:<\/p>\n

    \n
    • By dividing queries into types, the amount of data that the user has to retrieve when browsing your store decreases<\/strong>.<\/li>\n
    • lower amount of endpoints and requests sent to the backend relieves the database<\/strong>.<\/li>\n
    • increased control over the type and amount of retrieved data and requests<\/strong>.<\/li>\n
    • thanks to the query nesting and linking the time of development is shortened<\/strong>. Additionally, the server-to-client communication speed is increased<\/strong>.<\/li>\n
    • Magento allows for request and schema defining, which can optimize the server’s logic to your needs.<\/li>\n
    • By using Apollo GraphQL you are able to set request cache rules, optimize data interchange, and increase the website efficiency.<\/li>\n<\/ul>\n

      As you can see GraphQL offers more flexible and effective solutions for app optimization for Magento 2. Just like the platform from Adobe draws hundreds of thousands of businesses with its abilities of in-depth enhancement and personalization, so does GraphQL with its numerous ways of communication refinement and optimization strategies. The only thing that you need to do is to find a way for it to help you in your business.<\/p>\n","protected":false},"excerpt":{"rendered":"

      If we were to learn something from the IT industry, it would certainly be the fact that everything can be optimized. Surely, it won’t always be a big change, however, your solution is going to be better. It shows that progress is not rapid and sudden. During the majority of the time, the process of […]<\/p>\n","protected":false},"author":12,"featured_media":8046,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"yoast_head":"\n