Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/manav-khandurie/rate-limiter-service-poc-aws
A Rate-Limiter-Service proof of concept which would act as rate limiter to provide a middleware service
https://github.com/manav-khandurie/rate-limiter-service-poc-aws
aws hackthon lambda python rate-limiter reactjs redis
Last synced: 19 days ago
JSON representation
A Rate-Limiter-Service proof of concept which would act as rate limiter to provide a middleware service
- Host: GitHub
- URL: https://github.com/manav-khandurie/rate-limiter-service-poc-aws
- Owner: Manav-Khandurie
- License: gpl-3.0
- Created: 2024-04-19T07:26:50.000Z (9 months ago)
- Default Branch: main
- Last Pushed: 2024-06-04T21:40:09.000Z (7 months ago)
- Last Synced: 2024-10-27T18:37:02.225Z (2 months ago)
- Topics: aws, hackthon, lambda, python, rate-limiter, reactjs, redis
- Language: JavaScript
- Homepage: http://rate-limiter-bucket-upes.s3-website-us-east-1.amazonaws.com
- Size: 2.44 MB
- Stars: 1
- Watchers: 1
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# 
### About the Project
> The problem statement focuses on designing and implementing an effective rate limiting mechanism for API management to ensure fair and efficient usage of resources. The objective is to develop a system that prevents API abuse, optimizes resource allocation, and maintains high performance by applying various rate limiting strategies—Fixed Window, Sliding Window, Token Bucket, and Leaky Bucket. These strategies need to be adaptable based on parameters like request frequency, client identities, and available capacity.
### Tech Stack
         
### Contributing
1. Fork the Project
2. Clone your forked repository
```sh
git clone https://github.com//Rate-Limiter-Service-POC-AWS.git
```
3. Now go ahead and create a new branch and move to the branch
```sh
git checkout -b fix-issue-
```
4. After you have added your changes, follow the following command chain
* Check the changed files
```sh
git status -s
```
* Add all the files to the staging area
```sh
git add .
```
or
```sh
git add
```
* Commit your changes
```sh
git commit -m ""
```
5. Push your changes
```sh
git push origin fix-issue-
```
6. Open a Pull Request
>
> * Wait for the PR to be reviewed and merged.
>
> * Happy Coding!
### System Architecture
