Database Rate Limiting via Windowed Counters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database systems face challenges in managing excessive user postings, known as spam, which can overwhelm system resources and annoy community members, particularly in open networks where moderation is difficult and inefficient.

Innovation Solution

An extensible content moderation framework that allows for declarative configuration of moderation rules, enabling selective actions based on user and content criteria, including rate-limiting rules to control and manage user postings effectively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If open networks allow external users to post content freely, then user participation and community engagement are improved, but excessive spam postings overwhelm system resources and annoy members

Engineering Contradiction:
Improveuser participationVSAvoidspam postings
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary rate limiting checks before allowing content postings. By pre-establishing rate limits that track the number of postings within a time window and blocking postings that exceed these limits, the system prevents spam from overwhelming resources while still allowing legitimate user participation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The rate limiting mechanism acts as an intermediary between users and the database system. It monitors and controls posting rates, filtering out excessive spam postings before they reach the database, thereby protecting system resources while maintaining open network accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If rate limiting is implemented to control spam postings, then system resources are protected, but legitimate user postings may be restricted

Engineering Contradiction:
Improvesystem resourcesVSAvoiduser postings
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system uses configurable rate limit parameters (number of postings allowed within a time window) that can be adjusted to balance resource protection and user freedom. By tuning these parameters, the system can accommodate legitimate posting patterns while blocking spam, ensuring both reliability and ease of operation.

Inventive Principle:
Principle #35Parameter changes

3Manufacturing precision

If moderation rules are configured to filter spam, then content quality is improved, but system complexity increases

Engineering Contradiction:
Improvecontent qualityVSAvoidmoderation rules
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The moderation system is segmented into simple, modular rate limiting rules that can be independently configured and applied. Each rule operates as a discrete unit checking posting counts against thresholds, making the overall system manageable despite handling multiple users and communities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The rate limiting system operates autonomously without requiring complex manual moderation. It automatically tracks posting rates, applies configured limits, and blocks excessive postings without human intervention, maintaining content quality while minimizing operational complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10346370B2Rate limiting in a moderation framework of a database system
Publication Date: 2019.07.09 SALESFORCE INC
  • US10346370B2 patent drawing
  • US10346370B2 patent drawing
  • US10346370B2 patent drawing

AI summary

Some external users in a public on-line community may post excessive numbers of items, causing annoyance to others and unnecessary loading on database resources. A robust moderation framework enables an individual community moderator or admin to specify a set of rules and actions to mitigate this problem. Scalable, performant rate limiting rules employ windowed counters, separately for each rule, with the counters maintained in cache memory resources outside the main database.