New instrumentation that implements support for idempotency keys.#1572
Closed
ellebrecht wants to merge 6 commits intographql-java:masterfrom
Closed
New instrumentation that implements support for idempotency keys.#1572ellebrecht wants to merge 6 commits intographql-java:masterfrom
ellebrecht wants to merge 6 commits intographql-java:masterfrom
Conversation
Contributor
Author
|
Hi Andi, great meeting you at GraphQL Conf in Berlin, thanks again for the good talk. |
Member
|
Closing as out of date |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recently I had to implement support for idempotency keys in GraphQL mutations and would like to contribute the patch back to this wonderful project that I have used for almost two years now.
Idempotency keys are useful to guarantee at-most-once semantics in situations where a client may lose server responses (in my case connectivity or power loss) and implements retry mechanisms.
In my use case we have opted for Relay-compliant mutations and reuse the mandatory
clientMutationIdinput field as idempotency key.I have provided abstractions to make it easy to adapt to other use cases as well.
Hope you find this useful.