Skip to content

Conversation

@BizUnix
Copy link

@BizUnix BizUnix commented Feb 11, 2025

In this implementation, a client is identified by an access token, which is included with every request to a resource. The server checks whether the client's request falls within the allowed limit. If it does, the request is processed; otherwise, it is restricted.

The repository is structured into several directories:

  • .github/workflows: Contains GitHub Actions workflows for continuous integration and deployment.

  • RateLimiter.DataStore: Contains classes and methods for data storage and retrieval, implementing interfaces for in-memory data storage mechanisms.

  • RateLimiter.Services: Presumably includes the core services that enforce the rate-limiting logic, such as tracking request counts and timestamps. Factory is used to create right rule service based on rule option provided.

  • RateLimiter.Tests: Contains unit tests to ensure the rate-limiting functionality works as intended.

  • RateLimiter: The main application code, including the entry point and RuleOptions settings.

Use cases (Future testing)

  • Inject this library in Web API middleware

@BizUnix BizUnix closed this Feb 18, 2025
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

Successfully merging this pull request may close these issues.

1 participant