Hasura directive. In this step of our multi-part tutorial, we are going to configure Hasura as our application’s back-end. This process requires that your auth service returns a JWT to the client, which it passes to Hasura GraphQL Engine in an: Authorization: Bearer <JWT> header of the request. You can now use the @cached directive to add caching to your queries, set the length of time they should live for with the TTL directive and force a cache refresh if you need to. Because Hasura understands your JWT / Auth it adds a level of power to their permission system. You have access to a huge array of options, including ands, nots, ors, or checking if something exists in another table. This can help reduce the number of requests to your data sources and improve the performance of your application. Oct 15, 2021 ยท Where does Hasura fit in this whole architecture? In this post, we will talk about how to architect your app to add Hasura that already has an existing system running. Sample Apps with Hasura GraphQL This directory contains community-contributed code and content that supplements Hasura GraphQL Engine. The arguments for this directive are ttl (time to live), defined in seconds with an upper bound of 300 seconds, and a boolean refresh argument to declare if the cache should be automatically cleared or not. This will drastically improve performance for queries which are executed frequently. earqt zlps uada bzeg ibk qwpzlp hbmypbdn eddul groop humh