https://github.com/vaibhavyadav-dev/user-task-queuing-with-rate-limiting

A Node.js Server demonstrating User Task Queuing with Rate Limiting.
https://github.com/vaibhavyadav-dev/user-task-queuing-with-rate-limiting

cicd clustering containers docker express jenkins nodejs rate-limiting

Last synced: about 2 months ago
JSON representation

A Node.js Server demonstrating User Task Queuing with Rate Limiting.

• Host: GitHub
• URL: https://github.com/vaibhavyadav-dev/user-task-queuing-with-rate-limiting
• Owner: vaibhavyadav-dev
• Created: 2024-09-30T14:29:36.000Z (3 months ago)
• Default Branch: main
• Last Pushed: 2024-10-02T07:28:29.000Z (3 months ago)
• Last Synced: 2024-10-17T07:05:15.101Z (2 months ago)
• Topics: cicd, clustering, containers, docker, express, jenkins, nodejs, rate-limiting
• Language: JavaScript
• Homepage:
• Size: 24.4 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# User-Task-Queuing-with-Rate-Limiting

- A Node.js API cluster with 2 replica sets and a route to handle a simple task. The task has a rate limit of 1 task per second and 20 task per min for each user ID. 

- Users will hit the route to process tasks multiple times, a queueing system to ensure that tasks are processed 

according to the rate limit for each user ID.

> [!NOTE] 

> - Jenkins CI/CD Testing Passed ✅.

> - For the sake of complexity I've not implemented shared memory or databases like redis or sql, to make it  to   production level we have to add shared databases or memory for centralized access.

> - Note that two replica does not know anything about another one, so if request is processed by one replica its request can go to another replica and IT IS violation of rate limiting.