Skip to content
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

[Discussion] How to limit or prevent accidental infinite loop scenarios #30

Open
GitBytes opened this issue Oct 16, 2019 · 0 comments
Open

Comments

@GitBytes
Copy link

GitBytes commented Oct 16, 2019

Pacifica Notifications version

v0.4.1+

Scenario:

If a user sets up a dispatcher in the wrong way but well enough to both accept messages and do a subsequent upload, there is no method of preventing an endless stream of uploads. This can result in a DDOS like scenario to occur both on network and storage resources.

Question:

What are some ways to help limit the number of allowed iterations on relational transactions so subscribed dispatchers do not run away with system resources?

Initial Proposals:

  • Forms of quotas
  • Rate limiting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant