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