I have a GraphQL API gateway and I am thinking about a way to acknowledge mutations locally by using some sort of storage while also submitting the mutation to the message queue for async processing Do you know about any good patterns besides the obvious caching practices that would make the GraphQL-powered edge layer more responsive and reliable?