In the current codebase, users can interact with the system without any limitation on the quantity or the types of interaction. This makes it possible for users to flood the unacceptable system. To avoid this a mechanism must be assembled to prevent the situation in the first place by putting rate limitations on the user interactions. Thirdly, those users that try to flood the system must be banned based on a rule-based policy. It is worth mentioning that different parts of the system must have different kinds of constraints.
To execute this, the following task list is suggested:
In the current codebase, users can interact with the system without any limitation on the quantity or the types of interaction. This makes it possible for users to flood the unacceptable system. To avoid this a mechanism must be assembled to prevent the situation in the first place by putting rate limitations on the user interactions. Thirdly, those users that try to flood the system must be banned based on a rule-based policy. It is worth mentioning that different parts of the system must have different kinds of constraints.
To execute this, the following task list is suggested: