-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Exponential Retry Mechanism with Idempotency Headers #79
Comments
Hi, please assign this to me. Also I had below doubts:
|
@git-ashug Hi no as this effects the underlying http request mechanism which is all one issue. Feel free to ask any questions you need to implement this. |
@git-ashug are you still working on this? @Cliftonz Can I work on this? |
Hello @charan2628 , I have raised a draft PR and asked some questions there to maintainers. If they don't respond, you can take it from here. Also, would be a great help if you too review the PR and let me know what to do next. Thanks! |
@git-ashug In RetryInterceptor response is null in the while condition for starting iteration |
Hi @charan2628 , you can take this task up. |
Thank you @git-ashug |
In order to enhance the resilience and reliability of our SDK, we would like to introduce an Exponential Retry mechanism for retrying failed requests. Additionally, to ensure the idempotent processing of requests, it's vital to incorporate support for providing an Idempotency Key as per the draft specified in the HTTP Idempotency Key Header Field.
The key requirements for this implementation include:
Exponential Retry Mechanism:
Idempotency Key Provisioning:
Idempotency-Key
and following the standards outlined in the draft.Configuration and Documentation:
Acceptance Criteria:
Update: You can reference the go-lang library to keep the method signature and configuration the same.
novuhq/go-novu#62
Please refer to the draft for further details on the HTTP Idempotency Key Header Field and ensure adherence to the specified standards while implementing this feature in the SDK.
The text was updated successfully, but these errors were encountered: