-
Notifications
You must be signed in to change notification settings - Fork 715
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
Tests for API flood resilience #4479
Comments
|
Rethinking Massa Public API Load Testing StrategyIntroduction: 1. Absence of Rate Limiting: 2. Exposure via Reverse Proxy: 3. Reevaluating Load Testing Priorities: Conclusion: |
Using the massa-test-framework, we can write functional tests that ensures:
Exposed Public APIs servers are resilient to Denial of Service attacks (if one attacker tries to flood it with requests, the server can still handle some of the normal API load)
A flood on the API does not impact negatively other modules (the server should still finalize blocks, allow bootstrap, etc.)
No memory leaks on the long run for API servers. See how we could do it easily (maybe with the
Related to the check of the limit: Calibrate and adjust APIs arguments limits #4475
Limits should be tested on a referance machine (e.g. k8s cluster).
The text was updated successfully, but these errors were encountered: