![]() Persist GraphQL queries using builtin GraphiQL Explorer tool On the Configuration Properties page, you should see that the GraphQL Persistent Queries permission is enabled. Select WKND Shared, then select Properties in the top navigation bar to open configuration properties. Navigate to Tools > General > Configuration Browser. Let’s review that GraphQL Persisted Queries are enabled for the WKND Site project in your AEM instance. Review GraphQL Persisted Queries configuration setting Use cache-control parameters with persisted queries. ![]() Persist GraphQL queries with parameters.Please ensure that the previous chapter has been completed before proceeding with this chapter. This document is part of a multi-part tutorial. In this chapter, you persist the queries to AEM and learn how to use cache control on persisted queries. In the previous chapter, you have explored some advanced GraphQL queries to gather data for the WKND app. It is best practice and highly recommended to use persisted queries when working with the AEM GraphQL API. Persisted queries allow you to simplify your requests and improve security because your queries are encapsulated on the server and the AEM administrator has full control over them. While client-side GraphQL queries can also be executed using HTTP POST requests, which cannot be cached, persisted queries can be cached by HTTP caches or a CDN, improving performance. The benefit of this approach is cacheability. Clients can send an HTTP GET request with the query name to execute it. Persisted queries are queries that are stored on the Adobe Experience Manager (AEM) server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |