You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the task or feature?
Integrate rate limiting to handle NSE API’s rate limits more effectively.
Objective
Why is this important? I am not sure if NSE API imposes rate limits on API requests to prevent abuse and ensure fair usage. But, implementing rate limiting within our client will help manage limits (if any) effectively, avoid hitting rate limits, and ensure reliable access to the API without interruptions.
Approach
How should this be implemented?
Analyze the current NSE API rate limits and understand the constraints (e.g., requests per minute/hour).
Choose a rate limiting strategy (e.g., token bucket, leaky bucket).
Implement rate limiting in the API client to automatically handle and queue requests to stay within rate limits.
Add logic to handle rate limit exceeded errors gracefully and retry after the appropriate delay.
Document the rate limiting configuration and behavior in the project’s documentation.
Acceptance Criteria
Integrate rate limiting based on NSE API’s rate limit specifications.
Ensure that the client automatically handles rate limit errors and retries requests as needed.
Configure rate limiting parameters and provide options for adjusting them.
Document the rate limiting implementation and its usage.
Additional Information
Priority: Low
Dependencies: Understanding of NSE API’s rate limit policies and any existing request handling mechanisms.
Notes: Ensure the rate limiting logic does not significantly impact the performance or user experience and that it handles edge cases effectively.
The text was updated successfully, but these errors were encountered:
Summary
What is the task or feature?
Integrate rate limiting to handle NSE API’s rate limits more effectively.
Objective
Why is this important?
I am not sure if NSE API imposes rate limits on API requests to prevent abuse and ensure fair usage. But, implementing rate limiting within our client will help manage limits (if any) effectively, avoid hitting rate limits, and ensure reliable access to the API without interruptions.
Approach
How should this be implemented?
Acceptance Criteria
Additional Information
Priority: Low
Dependencies: Understanding of NSE API’s rate limit policies and any existing request handling mechanisms.
Notes: Ensure the rate limiting logic does not significantly impact the performance or user experience and that it handles edge cases effectively.
The text was updated successfully, but these errors were encountered: